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

forge-srs

Skill2 starsChanged 5 months agoMITView on GitHub

Run Stage 1 of the Forge pipeline — requirements analysis. Use when the

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    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 pipeline/state.md to confirm this is a Forge project.

    line 19
  2. Very specific:

    Read agents/requirements-analyst.md to load the Requirements Analyst persona.

    line 24
  3. Distinctive:

    Ask the user to describe their project if they haven't already.

    line 26
  4. Distinctive:

    Follow the Requirements Analyst workflow: clarify, categorize, assign REQ-IDs, write acceptance criteria.

    line 27
  5. Very specific:

    Write pipeline/01-srs/srs.md per the Output Contract in the persona file.

    line 29
  6. Very specific:

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

    line 30

≈ “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:srs — Requirements Analysis

When to Use

  • User says /forge:srs
  • User wants to define requirements, write an SRS, or describe what to build
  • Working in a Forge project at Stage 0 or 1

Pre-flight Check

  1. Read pipeline/state.md to confirm this is a Forge project.
  2. Note the current stage. If stage > 1, inform the user this stage appears done and ask if they want to revise it.

Steps

  1. Read agents/requirements-analyst.md to load the Requirements Analyst persona.
  2. Adopt that persona completely — you are now the Requirements Analyst.
  3. Ask the user to describe their project if they haven't already. Gather: what the system does, who uses it, key constraints (technology, timeline, compliance).
  4. Follow the Requirements Analyst workflow: clarify, categorize, assign REQ-IDs, write acceptance criteria.
  5. Conduct a single bounded round of clarification questions (REQ-INTERACTIVE-CLARIFY-001) before writing pipeline/01-srs/srs.md — one batch, not a drip. Unanswered questions become documented assumptions in the SRS.
  6. Write pipeline/01-srs/srs.md per the Output Contract in the persona file.
  7. Run python3 ${CLAUDE_PLUGIN_DIR}/scripts/state-manager.py advance --to 1 to mark Stage 1 active.

Verification

After running, confirm:

  • pipeline/01-srs/srs.md exists with REQ-IDs and acceptance criteria
  • pipeline/state.md shows current_stage: 1

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 1

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