agentleFS
Sign inStart free
tonmoy007tonmoy007/forge-plugins/skills/forge-product/SKILL.md

forge-product

Skill2 starsChanged 5 months agoMITView on GitHub

Run Stage 2 of the Forge pipeline — product UX and PRD. Use when the

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 1 is distinctive, and 7 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 7

    Very specific

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

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

    If it exits non-zero, STOP: present its message verbatim and do not proceed — the prior stage must be completed first (or use …

    line 26
  2. Very specific:

    Read pipeline/state.md — confirm Forge project.

    line 30
  3. Distinctive:

    If stage > 2, inform the user this stage appears done and ask if they want to revise.

    line 32
  4. Very specific:

    Run python3 ${CLAUDE_PLUGIN_ROOT}/scripts/load-profile.py --cwd .

    line 33
  5. Very specific:

    Read agents/product-designer.md to load the Product Designer persona.

    line 37
  6. Very specific:

    Read pipeline/01-srs/srs.md to understand the requirements.

    line 39
  7. Very specific:

    Write pipeline/02-product-ux/prd.md and pipeline/02-product-ux/design-system.md per the Output Contract (or the profile-specified artifacts …

    line 41
  8. Very specific:

    Run python3 ${CLAUDE_PLUGIN_ROOT}/scripts/state-manager.py advance --to 2 to mark Stage 2 active.

    line 42

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

/forge:product — Product Design & UX

When to Use

  • User says /forge:ux or /forge:product
  • User wants wireframes, user flows, a PRD, or design system tokens
  • Working in a Forge project at Stage 1 or 2

Pre-flight Check

Entry gate (REQ-GATE-ENTRY-001) — before adopting the persona, verify the prior stage's artifact exists:

python3 ${CLAUDE_PLUGIN_ROOT}/scripts/state-manager.py preflight --stage 2

If it exits non-zero, STOP: present its message verbatim and do not proceed — the prior stage must be completed first (or use /forge:force-advance to skip intentionally).

  1. Read pipeline/state.md — confirm Forge project.
  2. Confirm pipeline/01-srs/srs.md exists. If not: "Stage 1 (SRS) must be completed first. Run /forge:srs."
  3. If stage > 2, inform the user this stage appears done and ask if they want to revise.
  4. Run python3 ${CLAUDE_PLUGIN_ROOT}/scripts/load-profile.py --cwd . --stage 2 to load project-type overrides. Pay special attention to replace_with (e.g., ML projects replace UX with data-pipeline-design; API projects skip wireframes) and skip_steps.

Steps

  1. Read agents/product-designer.md to load the Product Designer persona.
  2. Adopt that persona — you are now the Product Designer.
  3. Read pipeline/01-srs/srs.md to understand the requirements.
  4. Follow the Product Designer workflow: define personas, map user flows, describe wireframes, define design tokens. Apply the profile overrides from pre-flight — if replace_with is set, follow that mode instead (e.g., produce data-flow.md and data-schema.md for ML, or command-tree.md for CLI); skip steps listed in skip_steps; add steps and artifacts from additional_steps / additional_artifacts.
  5. Write pipeline/02-product-ux/prd.md and pipeline/02-product-ux/design-system.md per the Output Contract (or the profile-specified artifacts if replace_with is in effect).
  6. Run python3 ${CLAUDE_PLUGIN_ROOT}/scripts/state-manager.py advance --to 2 to mark Stage 2 active.

Verification

After running, confirm:

  • pipeline/02-product-ux/prd.md exists with user flows (UF-IDs)
  • pipeline/02-product-ux/design-system.md exists with color/font/spacing tokens
  • pipeline/state.md shows current_stage: 2

Next Step

Derive the hint from the canonical stage table — never hardcode it (REQ-NEXTHINT-001, single source of truth). Run the helper and present its output to the user verbatim:

python3 ${CLAUDE_PLUGIN_ROOT}/scripts/state-manager.py next-hint --stage 2

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