devflow-feat
npx machina-cli add skill docutray/docutray-claude-code-plugins/devflow-feat --openclawDevFlow: Feature Specification Flow
Generate complete technical specifications and create GitHub issues with detailed acceptance criteria, impact analysis, and all information necessary for implementation.
When to Use
Use this flow when you need to:
- Create a new feature specification
- Plan a bug fix with proper documentation
- Define tasks with clear acceptance criteria
- Create technical documentation for implementation
Flow Diagram
flowchart TD
A([BEGIN]) --> B[Request feature description from user]
B --> C[Load project templates and conventions]
C --> D[Analyze codebase architecture]
D --> E[Verify GitHub connectivity]
E --> F{Information sufficient?}
F -->|No| G[Ask critical clarification questions]
G --> F
F -->|Yes| H[Generate technical specification]
H --> I{User approves specification?}
I -->|No| J[Revise based on feedback]
J --> I
I -->|Yes| K[Verify and create GitHub labels]
K --> L[Create GitHub issue with specification]
L --> M([END: Inform user - use /flow:devflow-dev next])
Node Details
1. Request Feature Description
Ask the user for a high-level description of what they want to implement.
2. Load Project Templates
Read .claude/details/commands/feat.md if it exists for project-specific templates.
3. Analyze Codebase
Review existing architecture to understand:
- Affected components
- Integration points
- Technical constraints
4. Generate Specification
Create comprehensive specification including:
- Clear description
- Motivation
- Acceptance criteria
- Technical approach
- Affected components
- Testing strategy
- Dependencies
5. User Approval
Present the full specification to the user and wait for approval before creating the issue.
6. Create Issue
Create the GitHub issue with appropriate labels and inform the user of the next step.
Output
After completion, the user will have:
- A GitHub issue with complete specification
- Appropriate labels applied
- Clear next step:
/flow:devflow-dev issue#<number>
Example Usage
/flow:devflow-feat
Then follow the interactive prompts to define your feature.
Source
git clone https://github.com/docutray/docutray-claude-code-plugins/blob/main/.kimi/skills/devflow-feat/SKILL.mdView on GitHub Overview
DevFlow-feat automates producing complete technical specifications and GitHub issues with acceptance criteria, impact analysis, and implementation details. It guides you from initial description through template loading, codebase analysis, and approved specification to a labeled GitHub issue ready for tracking.
How This Skill Works
The flow prompts for a high-level feature description, loads project templates, and analyzes the codebase to identify affected components and constraints. After generating a comprehensive specification, it presents it for user approval; upon approval, it creates a GitHub issue with appropriate labels and informs the user of the next steps.
When to Use It
- Create a new feature specification
- Plan a bug fix with proper documentation
- Define tasks with clear acceptance criteria
- Create technical documentation for implementation
- Prepare a GitHub issue with acceptance criteria and labels
Quick Start
- Step 1: Request a high-level feature description from the user
- Step 2: Load project templates (from .claude/details/commands/feat.md if available) and analyze the codebase
- Step 3: Generate a complete specification and present it for user approval before creating the GitHub issue
Best Practices
- Start with a concise high-level description to anchor scope
- Load project templates from .claude/details/commands/feat.md if present
- Analyze codebase architecture to identify affected components and constraints
- Generate a detailed specification including motivation, acceptance criteria, and testing strategy
- Obtain user approval before creating the GitHub issue and applying labels
Example Use Cases
- Add passwordless login feature with acceptance criteria and testing plan
- Fix export CSV bug with reproducible steps and impact analysis
- Create bulk data import task with dependencies and UI changes
- Document API change and create a task list for backend and client
- Plan code refactor task and associated tests with risk assessment