Skip to content

OJO PRODUCT EDUCATION / SKILL SELECTION

Which OJO Skill Should You Use?Start with the decision, not the catalog.

Choose the Agent Team for the whole job, then add the smallest set of OJO Skills needed for the current product decision. This guide maps common goals to a practical starting combination.

OJO / PRODUCT EDUCATION04 DECISIONS
SKILL OR REVIEW METHOD

Product Requirements Analysis

Input
User, problem, business goal, constraints, and existing evidence.
Output
Positioning, assumptions, non-goals, and prioritized scope.
Human checkpoint
Does the scope reflect evidence rather than an attractive feature list?

Choose a stage to inspect the input, output, and human decision.

Follow one task from user goal to Agent Team, Skills, review, and result.

THE PRODUCT DECISION

What is the smallest useful combination of Agent Team and Skills for the decision in front of the team?

DIRECT. MAKE. REVIEW.

Choose around the next decision.

A long Skill list is not a workflow. Start with the outcome, identify the stage, and add only the methods needed to produce and review the next useful artifact.

Your Agent Team applies the right Skills.

  1. 01

    01 / GOAL

    Name the next decision.

    Define whether the team needs product clarity, structure, visual direction, implementation, or quality review. Avoid asking one Skill to solve the entire project.

    A clear task, audience, constraints, and expected output.

  2. 02

    02 / TEAM + SKILLS

    Choose the owner, then the methods.

    Use an Agent Team for the complete job. Add a focused starting set of Skills for the current stage, then add specialist Skills only when the work creates a real need.

    One Agent Team, a small starting set, and optional additions.

  3. 03

    03 / REVIEW

    Change the Skill set as the work changes.

    Review the artifact against the brief. Keep useful decisions, remove methods that are no longer needed, and add the next Skill only when the project moves to another stage.

    A reviewed output and an explicit next decision.

A PRACTICAL STARTING SYSTEM

Match the Skill set to the work in front of you.

Use the guide below as a starting point. Confirm the exact Skill availability and behavior in the current OJO product before relying on it for delivery.

RECOMMENDED SEQUENCE

Move one reviewable artifact at a time.

  1. 01

    Clarify an idea

    Product Requirements Analysis

    Input
    User, problem, business goal, constraints, and existing evidence.
    Output
    Positioning, assumptions, non-goals, and prioritized scope.
    Review
    Does the scope reflect evidence rather than an attractive feature list?
  2. 02

    Structure the experience

    Product Page Information Architecture

    Input
    Confirmed requirements and the primary task to support.
    Output
    Information architecture, page hierarchy, and wireframe direction.
    Review
    Can a user find and complete the primary task?
  3. 03

    Improve existing work

    Design Audit → Design Refine

    Input
    Current design, brief, target audience, and known problems.
    Output
    Prioritized findings followed by a reasoned revision.
    Review
    Did the revision solve the diagnosed issue without discarding what worked?
  4. 04

    Prepare delivery

    Handoff → Frontend review

    Input
    Approved flow, responsive states, components, and constraints.
    Output
    Implementation guidance, quality findings, and a reviewable interface.
    Review
    Are behavior, accessibility, and engineering constraints explicit?

HUMAN REVIEW

Before moving forward

  • Every Skill has a clear job in the current stage.
  • The expected output can be reviewed by a person.
  • Optional Skills are added because of evidence, not because they are available.
  • The next stage starts only after the current artifact is accepted.

BOUNDARIES

What this workflow does not prove

  • A Skill recommendation is not proof that the underlying product assumption is correct.
  • Community and optional Skills may have different availability from core Agent Team capabilities.
  • Generated design and code still require accessibility, technical, and business review.

FROM CAPABILITY TO OUTCOME

Use fewer Skills with clearer jobs.

The recommended combinations are starting points, not automatic proof of product quality. The user remains responsible for evidence, constraints, and final judgment.

  • Task-to-Skill recommendation
  • Expected inputs and outputs
  • Human review checkpoint

PRODUCT QUESTIONS, ANSWERED

Before you assemble the team.

Should I add every relevant OJO Skill at the start?

No. Choose the Agent Team for the overall job and add the smallest set needed for the current stage. A Skill should have a clear reason, input, and expected output.

What is the difference between an Agent Team and a Skill?

An Agent Team coordinates a complete task across shared context. A Skill contributes a reusable method or review standard at a specific stage of that task.

Can I change Skills during a project?

Yes. Product analysis, page structure, visual refinement, motion, and delivery require different methods. Change the Skill set when the decision and artifact change.

Does the recommended combination replace expert review?

No. Skills make methods reusable, but product evidence, user validation, accessibility review, technical feasibility, and final approval remain human responsibilities.

BRING THE CAPABILITY INTO YOUR WORK

Choose the next capability.Keep the whole workflow in context.

Choose Skills in OJO

OJO brings product and business thinking, a design-aware Agent Team, specialist Skills, and thoughtful review into one workspace.