speclisted

Use when building a requirements spec or design brief before code — formalizing capture, decisions, and validation gates for non-trivial or enterprise-style work. Traceability + human-owned validation before handover. Common triggers: spec, specify requirements, requirements spec, requirements capture, design brief, decision register, requirements traceability, traceable requirements, validation gate, readiness gate, handover package, spec before build, truth spine, requirements-driven, requirements engineering, formalize requirements, requirements specification, engineering contract, invariant, proof obligation, counterexample, compatibility-sensitive, material requirement.
MarkBovee/agent-skills-kit · ★ 1 · AI & Automation · score 72

Install: claude install-skill MarkBovee/agent-skills-kit

# ASK Spec Formalize agreed intent into one traceable specification and engineering contract before development. Humans own decisions; downstream agents should not need to rediscover intent. ## Proportionality - **Trivial** — skip heavy spec; use `intake` or direct execution. - **Normal** — requirements, decisions, constraints, non-goals, and observable acceptance criteria. - **Complex, risky, or release-sensitive** — add relevant assumptions, invariants, proof obligations, counterexamples, dependencies, compatibility constraints, change impact, and audit expectations. Classify requirements by impact: **ordinary** = local behavior; **material** = violation could affect behavior, correctness, data, compatibility, architecture, ownership, routing, security, production safety, or release readiness; **critical** = material with severe potential impact. Material and critical requirements need deeper detail. Use impact, not numeric scoring or document size. Do not catalogue every edge case. ## Flow **Capture** — record need, context, goals, scope, non-goals, stakeholders, constraints, risks, dependencies, compatibility boundaries, open questions, and assumptions. Flag ambiguity; never assume. **Structure** — produce one contract containing requirements, decisions, constraints, must-remain-unchanged behavior, non-goals, invariants, acceptance criteria, proof obligations, dependencies, compatibility, and change impact. Decisions record choice, owner, rationale, and status: `prop