agentleFS
Sign inStart free
fusebase-devfusebase-dev/fusebase-flow/.agents/skills/product-owner/SKILL.md

product-owner

Skill9 starsChanged 28 days agoMITView on GitHub

Use when the operator types /product-owner, asks to activate Product Owner, start a Product Owner or PO session, or searches /product in Codex for Fusebase Flow project management. Do NOT use for implementing code; route implementation to the AI Developer role.

12 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 5 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 12 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read the Product Owner role body, preferring .codex/agents/product-owner.md on Codex and falling back to agents/product-owner/AGENT.md.

    line 51
  2. Very specific:

    Start Specify for intake-forms.

    line 60
  3. Very specific:

    If the canonical agent contradicts this bridge, follow agents/product-owner/AGENT.md and update this skill later.

    line 81
  4. Very specific:

    If Codex still does not show this skill after mirrors are regenerated, inspect .codex-plugin/plugin.json and …

    line 82
  5. Distinctive:

    If the operator needs code work, prepare an AI Developer handoff or ask them to start the AI Developer role.

    line 83
  6. Distinctive:

    Do not duplicate the full Product Owner agent body here.

    line 87
  7. Distinctive:

    Do not treat this skill as a new role definition.

    line 88
  8. Distinctive:

    Do not use this skill for Product Owner-adjacent implementation work.

    line 89
  9. Distinctive:

    Do not promise bare custom slash-command parity in Codex.

    line 90

“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Product Owner

Style: Mode-B-lite. Codex-visible activation bridge for the canonical Fusebase Flow Product Owner role. This skill exists so Codex skill discovery can find "Product Owner" even though the full role body lives in the role agent files.

Purpose

Activate the Product Owner workflow on surfaces where agents are not first-class slash commands. The canonical role instructions remain in agents/product-owner/AGENT.md and the Codex mirror .codex/agents/product-owner.md; this skill only routes discovery and activation.

When to invoke

  • Operator types /product-owner.
  • Operator asks to activate Product Owner, start a PO session, or use the Product Owner role.
  • Operator searches /product or /skills in Codex and expects the Product Owner option.
  • A new ticket needs Product Owner phases: Specify, Clarify, Plan, Decisions, Tasks, Verify, Review, or deploy handoff drafting.

Do not invoke when

  • The operator asks to implement, fix, test, or deploy code directly; use the AI Developer role/handoff path.
  • The task is /onboard or project vision capture; project-onboarding owns that flow after Product Owner activation.
  • The task is product documentation design; product-docs-first owns that workflow.
  • The task is app decomposition; product-apps-decomposition owns that workflow.

Required inputs

InputWhere it livesIf missing
Always-on Flow rulesFLOW_RULES.md down to ## Amendment logStop and read before acting
Product Owner role disciplineflow-skills/role-discipline/references/product-owner.mdStop and read before acting
Canonical Product Owner role bodyagents/product-owner/AGENT.mdUse .codex/agents/product-owner.md; if both are missing, stop and report mirror/canonical drift
Codex Product Owner mirror.codex/agents/product-owner.mdUse canonical agents/product-owner/AGENT.md and report that mirror-agents.sh should be run

Procedure

  1. Read the Product Owner role body, preferring .codex/agents/product-owner.md on Codex and falling back to agents/product-owner/AGENT.md.
  2. Execute the role body's activation boot exactly enough to satisfy its PO-BOOT-BLOCK / PO-ACTIVATED checks; do not paste or fork the full role body into this skill.
  3. Continue as Product Owner under the eight-phase flow, starting at Specify unless the operator provides an active artifact or phase.
  4. Route any implementation request to an AI Developer handoff or fresh AI Developer session; do not write production code as Product Owner.

Worked example

  1. Input: operator types /product-owner in Codex and says "Let's ship intake forms."
  2. Load .codex/agents/product-owner.md; emit Product Owner self-attestation plus PO-ACTIVATED.
  3. Start Specify for intake-forms; produce clarify questions or a spec draft.

Output artifacts

ArtifactPath or locationMode
Product Owner activationChatMode A
Spec/planning artifacts, when the operator proceedsdocs/specs/<slug>/Mode B
Implementation relay, when lockeddocs/tmp/handoff/<date>-<slug>-implement.mdMode B

Failure cases

Failure modeDetectionResponse
Product Owner role body missingNeither canonical nor Codex mirror existsStop; report Flow agent surface drift
Codex mirror missing only.codex/agents/product-owner.md absent, canonical existsUse canonical role body; report mirror regeneration needed
Operator asks for implementationRequest targets code edits/tests/deployProduce/point to AI Developer handoff; do not implement as Product Owner
Activation skippedNo PO-ACTIVATED marker or role self-attestationRe-run activation from the role body before continuing

Escalation path

  • If the canonical agent contradicts this bridge, follow agents/product-owner/AGENT.md and update this skill later.
  • If Codex still does not show this skill after mirrors are regenerated, inspect .codex-plugin/plugin.json and .agents/skills/product-owner/SKILL.md.
  • If the operator needs code work, prepare an AI Developer handoff or ask them to start the AI Developer role.

Anti-patterns

  • Do not duplicate the full Product Owner agent body here.
  • Do not treat this skill as a new role definition; it is a discovery bridge.
  • Do not use this skill for Product Owner-adjacent implementation work.
  • Do not promise bare custom slash-command parity in Codex; Codex exposes reusable workflows through skills/plugins.

Clean-room note

Original Fusebase Flow content. Designed after reviewing public AI coding workflow patterns; no third-party code, prompts, skill files, or hook scripts are copied. See docs/source-map.md.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free