Generate structured technical specifications with acceptance criteria and risk validation.
npx skills add https://github.com/kekemoto/skills --skill harness-spec
Please help me install this Agent Skill. Skill: harness-spec Source: https://github.com/kekemoto/skills/tree/main/skills/harness-spec Command: npx skills add https://github.com/kekemoto/skills --skill harness-spec
This skill addresses the ambiguity in software development by forcing a clear distinction between what needs to be achieved and how it is implemented, preventing scope creep and ensuring verifiable outcomes.
Use the harness-spec skill to draft a new specification for the user authentication module within the current project.
High-intent search queries and answers about installing and using this skill.
To write technical specifications for predictable PRs, draft a structured spec file defining clear acceptance criteria and verifiable outcomes. This enforces a WHAT-over-HOW documentation standard, separating project scope from implementation details to prevent scope creep.
A WHAT-over-HOW documentation standard for software development focuses strictly on defining acceptance criteria and verifiable outcomes rather than implementation details. This approach prevents ambiguity and scope creep by standardizing what needs to be achieved over how it is built.
You can manage feature-based PR workflows using project-scoped directories by generating structured specifications tied to specific project paths. This approach validates requirements against risk criteria and establishes clear dependency ordering for software development units.
Yes, you can validate development requirements against risk criteria before implementation. The specification generation process assesses potential risks during the drafting phase, ensuring the implementation roadmap has verifiable outcomes and clear acceptance criteria.
harness-spec works for standardizing development specs across multiple features by operating within project-scoped directories. It manages feature-based PR workflows and validates dependency ordering, ensuring each unit of work maintains consistent acceptance criteria.
Enforcing acceptance criteria over implementation details in software specs intentionally limits documentation to verifiable outcomes. This means the generated specification will not provide implementation roadmaps, requiring developers to determine the HOW independently during the development phase.
Fr-e-dAnalyze project directory structures to generate architectural summaries.
harishgovardhandamodarDecompose specifications into ordered tasks with acceptance criteria and dependencies.
dangelesVerify task completion against acceptance criteria and generate a verification report.
zircoteResearch, outline, draft, and refine content with citations.
