Generate a feature specification covering context, goals, risks, and testing.
npx skills add https://github.com/arthur-debert/dodot --skill to-spec-arthur-debert
Please help me install this Agent Skill. Skill: to-spec Source: https://github.com/arthur-debert/dodot/tree/main/.agents/skills/to-spec Command: npx skills add https://github.com/arthur-debert/dodot --skill to-spec-arthur-debert
This Skill helps you turn an early product idea, conversation, or rough codebase understanding into a structured, authoritative feature spec so the team can align before deeper architectural decisions are made.
Ask the assistant to turn your current product idea and repository context into a spec and write it to docs/spec as the first planning artifact.
High-intent search queries and answers about installing and using this skill.
To create a feature spec, you provide a product idea and repository context so the tool can generate an authoritative document covering context, problem, goals, non-goals, risks, and testing. This structured output serves as the first planning artifact.
Structuring product requirements for early planning requires covering context, problem, goals, non-goals, proposed shape, stories, risks, and testing. This comprehensive coverage ensures team alignment before deeper architectural decisions.
You need a feature specification before architectural review when a team requires a first-pass planning artifact to align on what should be built, why it matters, and how success will be verified prior to ticket creation.
Writing product requirements with non-goals and risks involves transforming conversation context and codebase understanding into a complete spec. This ensures structured coverage of boundaries and potential issues before development begins.
Yes, you can use a generated spec for ticket creation workflows. It is designed as the first planning step to establish a single source of truth, providing the necessary structure before proceeding to ticket breakdown.
A feature definition for roadmap planning should include context, problem, goals, non-goals, proposed shape, stories, risks, testing, and follow-up notes. This ensures an authoritative specification for the team.
AcendasGuides feature discovery conversations from vague ideas to structured plans and specs.
arthur-debertPlan a feature from loose ideas into a structured delivery workflow.
ByeongminLeeAnalyze codebases to generate and populate spec documents.
14790897Generate structured product requirement documents from unstructured problem statements.
