Convert user intent into a formal spec document with goals and acceptance criteria.
npx skills add https://github.com/chughtapan/safer-by-default --skill spec-chughtapan
Please help me install this Agent Skill. Skill: spec Source: https://github.com/chughtapan/safer-by-default/tree/main/skills/spec Command: npx skills add https://github.com/chughtapan/safer-by-default --skill spec-chughtapan
Ambiguity in user intent often leads to misaligned work. This skill converts vague goals into a formal spec that defines goals, non-goals, invariants, acceptance criteria, and open questions so downstream modalities can execute without needing the original conversation.
Provide a natural-language user intent and let the spec modality produce a complete artifact.
High-intent search queries and answers about installing and using this skill.
Converting vague intent into a formal spec involves structuring goals, non-goals, invariants, and acceptance criteria. This skill automates that conversion to prevent scope drift without requiring prior conversations.
Documenting open questions and assumptions for software requirements is best handled by generating a formal spec artifact. This process explicitly captures ambiguity and scope boundaries to guide downstream execution accurately.
To create and publish a requirements spec to GitHub as an issue, you provide a natural-language user intent. The generated spec artifact is then published directly to GitHub for traceability and team alignment.
Yes, when ambiguity is high, the spec generation process asks clarifying questions about the user intent. This proactive approach prevents misinterpretation and scope drift before the formal spec is finalized.
You can generate acceptance criteria and non-goals without prior discussion by inputting raw user intent. The skill independently produces a complete spec artifact designed to guide downstream work autonomously.
reason-healthcareConvert natural language feature ideas into structured, testable specs.
N0K0Convert GitHub issue or markdown feature specs into ordered file-level implementation checklists.
sidereal-ioOrchestrate Spec-Driven Development workflows and manage cycles with the Beads framework.
ArvorCoGenerate a structured PRD with goals, user stories, and acceptance criteria.
