feature

session:feature

Manage feature spec/plan lifecycle. Create new features during plan sessions, track progress during build sessions, and mark complete when finished.

Usage

/session:feature create <name>    - Create a new feature with spec and plan
/session:feature list             - List all features and their status
/session:feature show <name>      - Show feature details
/session:feature complete <name>  - Mark feature as complete
/session:feature archive <name>   - Archive a completed feature's plan

Instructions

/session:feature create

Creates a new feature directory with spec.md and plan.md from templates.

Best used during: PLAN sessions

Steps:

1. Validate feature name:

   • Must be lowercase, hyphenated (e.g., user-auth, payment-flow)
   • Cannot already exist

   ls -d .project/features/{{name}} 2>/dev/null && echo "EXISTS"
   

2. Create feature directory:

   mkdir -p .project/features/{{name}}
   

3. Gather feature information - Ask the user:

   • "What is this feature about?" (for Overview)
   • "What are the main goals?" (for Goals section)
   • "What should this feature NOT do?" (for Non-Goals)
   • "What are the key requirements?" (for Requirements)
   • "How will we know it's done?" (for Acceptance Criteria)

4. Create spec.md: Use the template from plugins/session-workflow/templates/feature-spec.md.template

   Fill in:

   • {{FEATURE_NAME}}: The feature name (title-cased)
   • {{STATUS}}: draft
   • {{CREATED_DATE}}: Today's date
   • {{UPDATED_DATE}}: Today's date
   • {{FEATURE_OVERVIEW}}: User's description
   • Goals, Non-Goals, Requirements, Acceptance Criteria from user input
   • Leave technical details as placeholders or ask if user wants to fill them

5. Create plan.md: Use the template from plugins/session-workflow/templates/feature-plan.md.template

   Ask the user:

   • "What's the implementation goal?"
   • "What's the current state before this feature?"
   • "What high-level changes are needed?"
   • "How should we break this into phases?"