Agentic Coding Spec

Agentic Coding Spec Router

Load this skill when a Builder prompt bridge request, explicit user request, or runtime diagnostic asks for roadmap, inventory, UNKNOWN assets, supporting sources, formal assets, prototype assets, confirm readiness diagnostics, or a spec-confirmed-implementation-request.

Do not load this skill solely because the user wrote a short acknowledgement such as 确认, confirmed, 可以, or 同意, or because the user confirmed an inline UI/design/implementation option in chat. For Phase 6.5 triggers and non-triggers, use skills/agentic-spec-confirmed-implementation/rules/phase65-trigger.md as the complete decision rule. This router may enter Phase 6.5 through Path A fenced JSON or Path B explicit natural-language automation request, but never through a bare acknowledgement or inline option confirmation.

Also load this skill after a local Superpowers spec is written or materially revised so it can route agentic-spec-reviewer before plan writing.

Requirement clarity P0B is documented as status: active; guarded pre-spec routing runs only after Phase 6.5 non-trigger decisions and durable source intake checks.

Required Context

• docs/solutions/l1/roadmap/builder-workspace-baseline-rules.md
• skills/agentic-coding-spec/rules/routing.md
• skills/agentic-coding-spec/rules/readiness.md
• skills/agentic-coding-spec/rules/commit-boundary.md
• For local Superpowers spec review, skills/agentic-spec-reviewer/SKILL.md.

Workflow

1. Identify the request category.
2. Load only the downstream skill needed for that category.
3. Run deterministic checks through agentic-spec doctor --workspace <path>.
4. For roadmap baseline or phase ledger work, use agentic-coding-roadmap.
5. For inventory classification, supporting source, or UNKNOWN repair work, use agentic-coding-inventory.
6. For local Superpowers specs, load agentic-spec-reviewer before superpowers:writing-plans; after review or revision closure, run derivation when required and always run agentic-prototype-trigger — its classification (including not_applicable with a skip reason) is the prototype gate.
7. For L1/L2/L3 formal asset derivation that is not a newly written or materially revised local Superpowers spec awaiting review, use agentic-spec-to-knowledge-derivation.
8. For prototype, DESIGN.md, or HTML preview generation requests, route through agentic-prototype-trigger; only an explicit refinement of an existing prototype manifest goes straight to agentic-prototype-refinement.
9. For spec-confirmed-implementation-request, use skills/agentic-spec-confirmed-implementation/rules/phase65-trigger.md as the complete trigger and non-trigger decision rule. This router may enter Phase 6.5 through Path A fenced JSON or Path B explicit natural-language automation request, but never through a bare acknowledgement or inline option confirmation. For validated requests, first run agentic-spec request validate --workspace <path> --request <request.json>, then load agentic-spec-confirmed-implementation; do not run local Superpowers gates for this request.

Guardrails

Do not push, tag, reset, rebase, stash, or force push. Refresh and phase commits run in the git_commit_scoped tier of skills/agentic-git-sync/rules/git-permission-boundaries.md.

Do not let agentic-spec decide business meaning. It only performs deterministic file operations and checks requested by the active skill or Agent.

For Phase 6.5 triggers and non-triggers, use skills/agentic-spec-confirmed-implementation/rules/phase65-trigger.md as the complete decision rule. This router may enter Phase 6.5 through Path A fenced JSON or Path B explicit natural-language automation request, but never through a bare acknowledgement or inline option confirmation.