feature-specify

I will help you create a feature specification following the specification workflow. This will capture user scenarios, requirements, and acceptance criteria in a structured format.

Usage:

• /feature-specify <brief description> - Create new feature spec
• /feature-specify --from-branch - Create spec from current git branch
• /feature-specify --show <feature-id> - Display existing spec

Instructions for me:

1. Generate feature ID:

   • If --from-branch: Use current git branch name

     git branch --show-current
     

   • Otherwise: Convert description to kebab-case (e.g., "JWT Authentication" → "jwt-authentication")
   • Max 50 characters
   • Format: {category}-{name} (e.g., auth-jwt, ui-dashboard, api-rate-limiting)

2. Check for existing spec:

   • Look for .mnemosyne/artifacts/specs/<feature-id>.md
   • If exists: Ask if user wants to update (increment version) or view
   • If updating: Parse current version and increment

3. Gather feature details (if creating new): Ask the user about:

   a) Feature Overview:

   • Feature name (human-readable)
   • Brief description (1-2 sentences)
   • Why this feature? (business value)

   b) User Scenarios (prioritized): For each scenario (start with P0/P1):

   • Priority: P0 (critical), P1 (high), P2 (medium), P3 (nice-to-have)
   • Actor: "As a [user type]..."
   • Goal: "I want [capability]..."
   • Benefit: "So that [value]..."
   • Acceptance Criteria: 3-7 specific, testable criteria

   c) Requirements:

   • Functional requirements
   • Non-functional requirements (performance, security, etc.)
   • Constraints or limitations

   d) Success Criteria:

   • How will we know this is successful?
   • What metrics matter?

4. Check constitution alignment:

   • Load .mnemosyne/artifacts/constitution/project-constitution.md
   • Verify feature aligns with core principles
   • Flag any conflicts (e.g., performance requirement vs. constitution)
   • If misaligned: Ask user to clarify or adjust

5. Format spec as markdown:

   ---
   type: feature_spec
   id: <feature-id>
   name: <feature-name>
   branch: <branch-name>
   version: 1.0.0
   status: draft
   created_at: <ISO 8601 timestamp>
   updated_at: <ISO 8601 timestamp>
   memory_id: <will be filled after storage>
   references: [<constitution-memory-id>]
   ---
   
   # Feature: <feature-name>
   
   ## Overview
   
   <brief description>
   
   **Business Value**: <why this matters>
   
   ## User Scenarios (Prioritized)
   
   ### P0: <Scenario Name>
   
   **As a** <actor>
   **I want** <goal>
   **So that** <benefit>
   
   **Acceptance Criteria**:
   - [ ] <criterion 1>
   - [ ] <criterion 2>
   - [ ] <criterion 3>
   
   ### P1: <Scenario Name>
   
   ...
   
   ## Requirements
   
   ### Functional
   - <requirement>
   
   ### Non-Functional
   - **Performance**: <requirement>
   - **Security**: <requirement>
   - **Scalability**: <requirement>
   
   ### Constraints
   - <constraint>
   
   ## Success Criteria
   
   - <criterion>
   
   ## Open Questions
   
   - [ ] <question needing clarification>
   
   ## Related
   
   - Constitution: `.mnemosyne/artifacts/constitution/project-constitution.md`
   - Parent Feature: <if sub-feature>
   

6. Write spec file:

   • Create .mnemosyne/artifacts/specs/<feature-id>.md
   • Ensure .mnemosyne/artifacts/specs/ directory exists

7. Store memory entry:

   • Use Mnemosyne CLI: mnemosyne remember
   • Arguments:
     • Content: Feature overview + first P0 scenario + "...see .mnemosyne/artifacts/specs/.md for full spec"
     • Namespace: project:<project-name> (detect from git)
     • Importance: 8 (specs are important)
     • Type: feature_spec
     • Tags: spec,feature,
     • Context: "Feature specification for "
   • Capture memory_id from output

8. Create memory link to constitution:

   • Get constitution memory_id from .mnemosyne/artifacts/constitution/project-constitution.md frontmatter
   • Link spec → constitution with relationship "builds_upon"
   • Update spec's references field in frontmatter