spec-anchored

Plugin spec-anchored from marketplace agent-plugins in risaddex/agent-plugins. Commands read from the repo's manifest — 2 days ago.

Skills (13)

• explain

  After a spec-anchored change, write a self-contained walkthrough of what was built and why. Use on explicit invocation. Reads the spec, the approved plan, and the diff. Does not invent intent from the code.

• general-code-review

  Rubric for the internal authoring general-code-reviewer. Use on one exact Owner candidate to fix concrete correctness, simplicity, local design, test, and type defects before mutation hardening. This pass is hardening, not approval.

• implement-backlog

  Unattended implementation of one qualified increment issue. Use only as an explicit launcher instruction. Every question becomes a named blocker. Never use for a new capability or for architecture.

• implement-feature

  Supervised implementation of one issue or spec slice. Use only when the user explicitly invokes implement or implement-feature. Human gates in session. Does not run headless.

• implement-orchestrated

  One orchestrator-owned issue, worktree, and pull request. Use only as the worker's explicit first instruction. Gates are mediated through the issue. Never starts from a casual mention.

• implement

  Explicit alias for supervised spec-anchored implementation. Use only when the user invokes implement. Follows implement-feature in full.

• implementation-protocol

  Shared spec-anchored state machine, phases 0-10. Load when an implement adapter says to. Does not start a run by itself.

• prep

  Prepare a repository's verification interface for spec-anchored work. Use only on explicit invocation. Detect and extend. Does not change application code and does not vendor the upstream kernel.

• review-spec-drift

  Report drift between one capability spec and its implementation. Use on explicit invocation. Report only. Does not edit the spec or the code.

• shape

  Interview toward a capability spec or a sharpened task. Use only when the user invokes shape or asks to grill an idea, transcript, brownfield area, existing spec, or issue. Never write or edit the spec file.

• spec-to-tickets

  Decompose one ratified capability spec into coherent delivery issues. Use only on explicit invocation. Drafts first, publishes only after the human confirms. Does not edit production code or the spec.

• ticket-readiness-review

  Review a proposed issue or issue batch before publication or dispatch. Checks that each issue is one coherent delivery contract. Report only. Does not edit tickets, plans, or code.

• to-spec

  Write or update a capability spec from a completed shape interview or supplied notes. Use only on explicit invocation. Does not interview. Gaps become open questions. Stable IDs are issued in continuation and never renumbered.

Similar plugins