AgentSkillsCN

devflow-feat

生成详尽的技术规格,并创建带有验收标准的 GitHub 问题。当用户希望在充分规划并实现与 GitHub 集成的前提下,创建新功能、修复缺陷或制定任务时,可使用此技能。触发短语包括:“创建功能”、“新建议题”、“技术规格”、“规划功能”、“/feat”。

SKILL.md
--- frontmatter
name: devflow-feat
description: Generate detailed technical specifications and create GitHub issues with acceptance criteria. Use when users want to create features, fixes, or tasks with proper planning and GitHub integration. Trigger phrases: "create feature", "new issue", "specification", "plan feature", "/feat"
type: flow

DevFlow: 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

mermaid
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

code
/flow:devflow-feat

Then follow the interactive prompts to define your feature.