requirement-draft

Transform raw feature input into structured requirement drafts under docs/feature/.

Updated May 31, 2025

Search Tags:#workflow #documentation #review #feature #draft #requirement

Ready to run

npx skills add https://github.com/dEitY719/dotfiles --skill requirement-draft

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requirement-draft
Source: https://github.com/dEitY719/dotfiles/tree/main/claude/skills/requirement-draft
Command: npx skills add https://github.com/dEitY719/dotfiles --skill requirement-draft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create and iterate on feature requirement draft documents to kick off new feature discussions, capture scope, and synthesize colleague feedback.

Core Features & Use Cases

Draft initial requirements: Generate structured scratch docs for new features under docs/feature/.
Collaborative review synthesis: Aggregate peer feedback across v1 and v2 cycles to unify directions.
Template-driven outputs: Produce consistent requirement documents using the v1/v2 workflow templates.

Quick Start

Invoke /requirement-draft v1 <input> to generate an initial feature draft.

Frequently Asked Questions about requirement-draft

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I draft feature requirements from raw input?▼

You can generate an initial requirement draft by invoking the /requirement-draft v1 command with your raw feature input. This creates a structured scratch document under the docs/feature/ directory, providing a template-driven format to kick off new feature discussions.

What is the best way to synthesize peer feedback into requirement documents?▼

The best way to synthesize peer feedback is using the v2 synthesis cycle. It aggregates cross-team review input from your v1 draft, unifying directions and recording the integration of colleague feedback directly into the final requirement document.

How does the v1 and v2 workflow template mechanism work?▼

The v1 and v2 workflow template mechanism separates requirement creation into two cycles: v1 generates the initial structured scratch doc from raw input, while v2 synthesizes peer feedback and aggregates reviews to unify the feature directions.

Do I need a specific project structure to generate feature requirement drafts?▼

You need a docs/feature/ directory structure to properly align and store the generated requirement drafts. The tool applies a template-driven format that organizes early-stage feature scoping directly within this documentation hierarchy.

When do I need a template-driven format for feature scoping?▼

You need a template-driven format for feature scoping when capturing early-stage requirements and facilitating cross-team collaboration. It ensures multiple review paths and peer feedback integration are recorded consistently across v1 creation and v2 synthesis cycles.