unkos-dev/specful
Skills for authoring and reviewing Specful artifacts, planning and implementing changes, and operating the CLI.
Use when recording a durable decision as a Specful ADR (architecture decision record), or superseding an accepted one.
Use when writing or updating a Specful Design: documenting how a subject of the system works, or connecting a Design to the Requirements it satisfies.
Use when the user asks to implement, execute, resume, or continue a saved change plan or arc plan step by step.
Use when the navigation indexes or catalog under docs/specs/ are missing or out of date after adding or editing a Requirement, Design, or ADR, or when checking whether they are.
Use when a change needs a persistent implementation plan, unresolved design choices must be settled before planning, or an arc must coordinate multiple deliverables.
Use when writing or updating a Specful Requirement: a new normative obligation, or a change to what the software must do.
Review a Specful Requirement, Design, ADR, or change for consequential substantive defects.
Use when looking up the catalog record for a specific Requirement, Design, or ADR identifier.
Use when following requirement-to-design links for a specific Requirement identifier, checking whether a Requirement has a satisfying Design, or listing the artifacts that cite an ADR.
Use when checking whether Specful Requirements, Designs, and ADRs pass schema and cross-reference validation, before committing a change to any of them, or when wiring the checks into an agent harness's hooks.