Create feature specifications with templates, checklists, and acceptance scenarios.
npx skills add https://github.com/mikemyl/verified-development --skill specify-mikemyl
Please help me install this Agent Skill. Skill: specify Source: https://github.com/mikemyl/verified-development/tree/main/skills/specify Command: npx skills add https://github.com/mikemyl/verified-development --skill specify-mikemyl
The 'specify' skill ensures that project features and functionality are properly understood and documented at the beginning, preventing miscommunication, scope creep, and reducing the time to market.
Specify the feature 'user authentication' by using the 'specify' skill. You'll need to create acceptance scenarios and provide an optional brief description of the feature.
High-intent search queries and answers about installing and using this skill.
Writing a requirement specification involves using guided templates to document feature intent, define project boundaries, and capture technical constraints. This specification process ensures feature intent and constraints are captured effectively, preventing scope creep and miscommunication.
The best way to manage requirements and prevent scope creep is creating comprehensive specifications with acceptance scenarios at the project start. Capturing feature intent and constraints early aligns stakeholder expectations and reduces time to market.
Create acceptance test scenarios for requirement specifications by following a guided specification creation process. This involves defining the feature description, outlining project context, and documenting specific scenarios to get stakeholder approval and align expectations.
Define project boundaries and technical architecture during the initial requirements definition phase before development starts. Establishing these constraints early ensures feature functionality is properly understood, documented, and approved by stakeholders.
Yes, you can use specification templates and checklists to define feature intent and capture constraints, providing structured tools to get stakeholder approval. Aligning expectations early through documented requirements prevents miscommunication during project delivery.
xiaoweidotnetGenerate structured technical specification documents defining project scope, architecture, and success criteria.
Codagent-AIConvert settled software requirements into approved technical design artifacts.
vinvcnGenerate a project specification before implementing new features.
iamsteveholmesCapture conversation story ideas into backlog stub files with index entries.
