FORGE
FORGE is an explicit workflow for bounded work: one task, clear scope, hard stops, evidence, and clean checkpoints.
Use it for governed implementation, planning, review, shipping, coordination, or context-safe bootstrap.
Routing
- Bootstrap or migrate docs:
forge-bootstrap
- Plan lifecycle work:
forge-plan
- Build/implement a task:
forge-build or forge-execute-task
- Review work:
forge-review
- Ship, release, or close out:
forge-ship
- Critique scope and assumptions:
forge-critique
- Run security review:
forge-security-review
- Check done/evidence:
forge-evaluation
- Read/update lessons:
forge-memory
- Manage private/public tool releases:
forge-tool-workflow
- Coordinate multi-repo shared-contract work:
forge-cross-project
Read references only when the current task requires them:
- team and branches:
references/team-mode.md
- repo flavors:
references/repo-flavors.md
- agent surfaces:
references/agent-flavors.md
- DevSecOps gates:
references/devsecops-gates.md
- app docs:
references/application-docs.md
- lifecycle map:
references/lifecycle-map.md
- skill anatomy:
references/skill-anatomy.md
- context and token discipline:
references/token-efficiency.md
Operating Model
- Read the minimum project-local context needed for the current step.
- Prefer
docs/forge/CONTEXT.md when present; otherwise use conservative lite defaults.
- Read
docs/forge/AI.md, the compact task index or configured task source, one selected task, and task-relevant source files.
- Do not load all FORGE docs, all tasks, all memory, or all security checklists at startup.
- Preserve one bounded checkpoint at a time: implementation, evidence, task state, and commit or PR/MR handoff.
- Stop on ambiguity, missing prerequisites, architecture conflict, unsafe operations, unresolved security concerns, or failed gates.
- Activation follows
activation_mode; repo-default routing requires that consent.
Team Mode
When multiple developers or agents work in parallel:
- use feature branches rather than direct work on shared branches
- claim one task before implementation
- require explicit
file_scope for executable tasks
- prefer issue assignment and labels when GitHub or GitLab is authoritative
- use append-only evidence and memory records where possible
- require CI and protected-branch merging
Output Discipline
Follow progress_policy in docs/forge/AI.md (default compact when absent):
concise checkpoint output, detailed blockers, one terminal summary — never
per-task recaps of what the task file and commit already record. Full protocol:
references/checkpoint-output.md.
1---2name: forge3description: Governed workflow for AI-assisted coding on a real repo. Triggers: bounded tasks, file scope, task ledgers, claim-before-implement, evidence trails, critique/review/security gates, or multi-agent/multi-repo coordination. Use on any mention of "FORGE", `docs/forge/`, or governed development, or when agents drift outside scope. Not for one-off edits or unstructured review.4---56# FORGE78FORGE is an explicit workflow for bounded work: one task, clear scope, hard stops, evidence, and clean checkpoints.910Use it for governed implementation, planning, review, shipping, coordination, or context-safe bootstrap.1112## Routing1314- Bootstrap or migrate docs: `forge-bootstrap`15- Plan lifecycle work: `forge-plan`16- Build/implement a task: `forge-build` or `forge-execute-task`17- Review work: `forge-review`18- Ship, release, or close out: `forge-ship`19- Critique scope and assumptions: `forge-critique`20- Run security review: `forge-security-review`21- Check done/evidence: `forge-evaluation`22- Read/update lessons: `forge-memory`23- Manage private/public tool releases: `forge-tool-workflow`24- Coordinate multi-repo shared-contract work: `forge-cross-project`2526Read references only when the current task requires them:2728- team and branches: `references/team-mode.md`29- repo flavors: `references/repo-flavors.md`30- agent surfaces: `references/agent-flavors.md`31- DevSecOps gates: `references/devsecops-gates.md`32- app docs: `references/application-docs.md`33- lifecycle map: `references/lifecycle-map.md`34- skill anatomy: `references/skill-anatomy.md`35- context and token discipline: `references/token-efficiency.md`3637## Operating Model38391. Read the minimum project-local context needed for the current step.402. Prefer `docs/forge/CONTEXT.md` when present; otherwise use conservative `lite` defaults.413. Read `docs/forge/AI.md`, the compact task index or configured task source, one selected task, and task-relevant source files.424. Do not load all FORGE docs, all tasks, all memory, or all security checklists at startup.435. Preserve one bounded checkpoint at a time: implementation, evidence, task state, and commit or PR/MR handoff.446. Stop on ambiguity, missing prerequisites, architecture conflict, unsafe operations, unresolved security concerns, or failed gates.457. Activation follows `activation_mode`; repo-default routing requires that consent.4647## Team Mode4849When multiple developers or agents work in parallel:5051- use feature branches rather than direct work on shared branches52- claim one task before implementation53- require explicit `file_scope` for executable tasks54- prefer issue assignment and labels when GitHub or GitLab is authoritative55- use append-only evidence and memory records where possible56- require CI and protected-branch merging5758## Output Discipline5960Follow `progress_policy` in `docs/forge/AI.md` (default `compact` when absent):61concise checkpoint output, detailed blockers, one terminal summary — never62per-task recaps of what the task file and commit already record. Full protocol:63`references/checkpoint-output.md`.
redteamlife