create-feature-unit

Create Feature Unit

Create a structured feature unit with specification, manifest, and test scaffolds.

When to Use

Use this skill when:

• User mentions "create feature", "new feature", "add feature", "implement feature"
• User references "feature unit" or configured abbreviation
• Feature Unit IDs mentioned (matching configured pattern in foundation-config.yaml)
• Feature descriptions implying new work (e.g., "we need to add X", "implement Y")
• Planning discussions about new functionality
• User explicitly invokes /create-feature-unit

Workflow

Step 1: Detection and Confirmation

1. Load configuration:

   • Read foundation-config.yaml for feature unit settings
   • Extract feature_units.directory and feature_units.id_pattern
   • Check if feature_units.enabled is true

2. Extract feature information from context:

   • Feature Unit ID (if mentioned, validate against configured pattern)
   • Feature name or description
   • Priority hints (P0/P1/P2/P3)
   • Scope hints (what functionality is mentioned)

3. Check if feature unit already exists:

   • Look in {configured_directory}/completed/{feature_id}/
   • Look in {configured_directory}/in_progress/{feature_id}/
   • Check repository-specific FU inventory (if configured)

   If exists → inform user and ask: "Do you want to modify it or create a new one? (modify/new)"

4. If feature unit does NOT exist:

   • Ask for confirmation:

     I see you're requesting a new Feature Unit. Should I create a Feature Unit spec 
     in `{configured_directory}/in_progress/{feature_id}/` following the Feature Unit 
     creation workflow? (yes/no)
     

5. If feature ID not detected:

   • Show configured ID pattern from config
   • Ask: "What Feature Unit ID should I use? (format: {configured_pattern}, e.g., FU-2025-01-001)"
   • Wait for user input before proceeding

6. Handle exceptions:

   • If user says "no" → do not proceed
   • If user says "just a spec document" → create spec only