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

forge-arch

Skill2 starsChanged 5 months agoMITView on GitHub

Run Stage 3 of the Forge pipeline — system architecture. Use when the

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 1 is distinctive, and 8 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.

  • 8

    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 > 3, ask if the user wants to revise architecture.

    line 33
  4. Very specific:

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

    line 34
  5. Very specific:

    Read agents/system-architect.md to load the System Architect persona.

    line 38
  6. Very specific:

    Read pipeline/01-srs/srs.md and pipeline/02-product-ux/prd.md.

    line 40
  7. Very specific:

    Follow the System Architect workflow: C4 diagrams, data model, API surface, security model, ADRs.

    line 41
  8. Very specific:

    Write pipeline/03-architecture/architecture.md, ADR files, and any profile-specified extra artifacts per the Output Contract.

    line 42
  9. Very specific:

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

    line 43

≈ “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:arch — System Architecture

When to Use

  • User says /forge:architecture or /forge:arch
  • User wants system design, C4 diagrams, data model, API contracts, or ADRs
  • Working in a Forge project at Stage 2 or 3

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 3

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: "Complete Stage 1 first (/forge:srs)."
  3. Confirm pipeline/02-product-ux/prd.md exists (warn if missing but don't block).
  4. If stage > 3, ask if the user wants to revise architecture.
  5. Run python3 ${CLAUDE_PLUGIN_ROOT}/scripts/load-profile.py --cwd . --stage 3 to load project-type overrides. Note any additional_concerns (e.g., ML: training/inference path, checkpoint format; fullstack: SSR/SSG strategy, BFF boundary; API: versioning, pagination, idempotency) and additional_artifacts (e.g., openapi-spec.yaml, route-manifest.md).

Steps

  1. Read agents/system-architect.md to load the System Architect persona.
  2. Adopt that persona — you are now the System Architect.
  3. Read pipeline/01-srs/srs.md and pipeline/02-product-ux/prd.md.
  4. Follow the System Architect workflow: C4 diagrams, data model, API surface, security model, ADRs. Address every additional_concerns item from the profile in the architecture doc, and produce any additional_artifacts listed.
  5. Write pipeline/03-architecture/architecture.md, ADR files, and any profile-specified extra artifacts per the Output Contract.
  6. Run python3 ${CLAUDE_PLUGIN_ROOT}/scripts/state-manager.py advance --to 3 to mark Stage 3 active.

Verification

After running, confirm:

  • pipeline/03-architecture/architecture.md exists with C4 diagrams and data model
  • At least one ADR exists in pipeline/03-architecture/adr/
  • pipeline/state.md shows current_stage: 3

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 3

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