Generates structured feature specifications with QA gate selection and optional council review.
npx skills add https://github.com/ZaxbyHub/ragappv3 --skill specify-zaxbyhub
Please help me install this Agent Skill. Skill: specify Source: https://github.com/ZaxbyHub/ragappv3/tree/main/.opencode/skills/specify Command: npx skills add https://github.com/ZaxbyHub/ragappv3 --skill specify-zaxbyhub
.swarm/spec.md with numbered functional requirements (FR-###), measurable success criteria (SC-###), Given/When/Then user scenarios, and [NEEDS CLARIFICATION] markers resolved through a critic-assisted clarification funnel. - Codebase Reality Checks & Archiving: Verifies referenced code actually exists before specifying, and archives prior spec versions to .swarm/spec-archive/ before overwriting. - Mandatory QA Gate Dialogue: Presents eleven quality gates (reviewer, test_engineer, sast, drift_check, council modes, and more) with defaults, then persists the user's election to .swarm/context.md so planning cannot proceed without it. - Optional Council Spec Review: When the council_general_review gate is enabled, runs web research and dispatches generalist, skeptic, and domain-expert agents in parallel to critique the draft spec. - External Plan Import: Reverse-engineers a spec from a user-supplied implementation plan and validates the plan against task-format rules. - Use Case: A developer says "specify a notification preferences feature" — the Skill scans the codebase, consults SME research, writes a technology-agnostic spec, asks the user to confirm QA gates and parallelization, then hands off to clarification or planning. ## Quick Start Ask the agent to specify a new feature, for example: "Specify a feature that lets users export their chat history from the vault."High-intent search queries and answers about installing and using this skill.
Invoke the specify mode by asking to "specify" or "define a feature". It generates a spec with user scenarios in Given/When/Then format, numbered functional requirements using MUST/SHOULD language, and measurable success criteria, written to .swarm/spec.md.
Provide the plan as pasted text or a file reference. The external plan import path reverse-engineers functional requirements and success criteria from the plan's tasks, validates task formatting, and reports gaps as advisory suggestions without silently rewriting your plan.
No. The spec content rules explicitly forbid technology stacks, framework names, file paths, API designs, and database schemas. The spec captures only what users need and why, keeping every requirement independently testable and implementation-agnostic.
You are asked whether to overwrite or refine. Overwriting first archives the existing spec to .swarm/spec-archive/ using its version or a date-based filename. Choosing refine delegates to the CLARIFY-SPEC mode instead of regenerating.
Gate selection is mandatory and cannot be skipped or defaulted silently. The eleven gates are presented with their defaults, and your election is written to .swarm/context.md because the planning step rejects execution if this section is missing.
Enable it for novel architecture, unclear best practices, or high-risk design decisions. It requires council.general.enabled set to true and a configured search API key; the skill runs web research and dispatches three council agents to critique the draft spec.
anthropicsGenerate structured PRDs and feature specifications from problem statements.
tomgunCreate implementation plans for software features with scope, files, acceptance criteria, and risks.
CidLucasAnalyze codebase architecture and propose module deepening refactorings.
XGanQAQClassify small gameplay changes and draft Quick Design Specs.