Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From A2Z FORGE
Create or update the living product goal and blueprint. Use when scope, north star, positioning, non-goals, success measures, or product decisions change.
How this skill is triggered — by the user, by Claude, or both
Slash command
/a2z-forge:forge-goalThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Read \`${CLAUDE_PLUGIN_ROOT}/references/WORKFLOW_PROTOCOL.md\` before mutating project state.
Read `${CLAUDE_PLUGIN_ROOT}/references/WORKFLOW_PROTOCOL.md` before mutating project state.
current evidence, intake, constraints, and requested change.
GOAL.md plus synchronized blueprint, decisions, risks, and project state.
Reconcile the request with evidence and deadline. State one central promise, user, wedge, success measures, scope, non-goals, and release definition. Record tradeoffs and superseded decisions.
Honor the current permission mode. Use only task-relevant tools and installed skills. Log consequential actions. Persist outputs before reporting success.
On tool failure, record the command, safe retry state, and blocker. Retry only idempotent work. Never convert a missing credential, unavailable provider, failed test, or incomplete adapter into a success claim.
`/forge-goal Narrow launch to teachers creating quizzes from PDFs.`
A scope change updates goal, task graph, risks, and non-goals without contradiction.
npx claudepluginhub jumpsy/a2z-forge --plugin a2z-forgeGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.