Generate and review a specification document before coding begins.
npx skills add https://github.com/sobhanashine/nazarato --skill spec-first-sobhanashine
Please help me install this Agent Skill. Skill: spec-first Source: https://github.com/sobhanashine/nazarato/tree/main/.agents/skills/spec-first Command: npx skills add https://github.com/sobhanashine/nazarato --skill spec-first-sobhanashine
This Skill helps prevent scope creep and ensures all stakeholders agree on the scope of a new feature before development begins.
Generate a spec for a new feature by using the 'spec-first' skill and follow the four questions outlined in the documentation.
High-intent search queries and answers about installing and using this skill.
Preventing scope creep requires creating a documented specification before coding begins. This approach aligns stakeholders on project requirements, ensuring all parties review and explicitly agree on the feature scope before implementation starts.
A feature specification document should include the problem, user action, data changes, and failure modes. Generating this detailed spec ensures stakeholders agree on requirements before any code is written.
Getting stakeholder agreement involves creating a short spec document outlining the feature scope and securing explicit sign-off. You must generate and review the specification before proceeding with implementation.
You need to create a specification document whenever starting a new feature or task in agile development. Generating a spec first ensures documented requirements exist before coding begins.
The best way to manage feature scope is enforcing a spec-first workflow that mandates a one-page specification before coding. This prevents undocumented requirements and aligns stakeholders on the project scope.
No, you cannot write code before the specification is agreed upon. This approach requires generating and reviewing a spec document, securing explicit stakeholder sign-off, and only then proceeding with implementation.
cshyangPlan and execute a project discovery phase to define requirements and scope.
coff33ninjaWrite specifications defining goals, constraints, and acceptance criteria before coding.
johnatas-henriqueAggregate sprint metrics and flag stale tasks from plan and story files.
mathiasbourgoinGenerate formal Rocq or Quint specifications from validated markdown product specs.
