From this repository:
node ./bin/agentic-workflow.mjs init /path/to/your/repoUse --force only when you intentionally want to overwrite existing workflow files.
The installer writes:
.agentic/workflow.jsonAGENTS.md.github/copilot-instructions.md.github/instructions/tests.instructions.md.github/prompts/*.prompt.md.vscode/mcp.json
Run:
node ./bin/agentic-workflow.mjs validate .In this repository, the same check is available through:
npm run validateEdit .agentic/workflow.json in the consuming repository. Keep these invariants:
- Every role has a unique
id. - Every
handoffTotarget exists. - Every phase references an existing role.
- Every quality gate names required evidence.
Use the prompt files from .github/prompts when you want a specific phase. Keep AGENTS.md and .github/copilot-instructions.md short because they are broad instructions that may be applied frequently.
Start with the minimal .vscode/mcp.json template. Add more servers only when they provide evidence the workflow actually needs. Keep secrets outside the repository and prefer existing authenticated CLIs or local secret stores.
- Install into one active repository.
- Run one issue through all five phases.
- Record missing gates or noisy instructions.
- Tighten
.agentic/workflow.json. - Add CI validation before rolling out to more repositories.