specsmd 0.0.0-dev.31 → 0.0.0-dev.33

package/flows/simple/README.md

@@ -79,12 +79,11 @@ Or ask: "What's the next task for user-auth?"
 ## Output Structure
 
 ```
-memory-bank/
-└── specs/
-    └── {feature-name}/
-        ├── requirements.md    # Phase 1: What to build
-        ├── design.md          # Phase 2: How to build it
-        └── tasks.md           # Phase 3: Step-by-step plan
+specs/
+└── {feature-name}/
+    ├── requirements.md    # Phase 1: What to build
+    ├── design.md          # Phase 2: How to build it
+    └── tasks.md           # Phase 3: Step-by-step plan
 ```
 
 ## EARS Format
@@ -141,7 +140,7 @@ src/flows/simple/
 | **Target** | Quick feature specs | Full development lifecycle |
 | **Phases** | 3: Requirements → Design → Tasks | 3: Inception → Construction → Operations |
 | **Agents** | 1 (Agent) | 4 (Master, Inception, Construction, Operations) |
-| **Output** | 3 markdown files | Full memory-bank hierarchy |
+| **Output** | 3 markdown files | Full artifact hierarchy |
 | **DDD Stages** | Not included | Full DDD stages in Construction |
 | **Bolts** | No concept | Time-boxed execution sessions |
 | **Hierarchy** | Flat (specs/) | Nested (intents/units/stories) |

package/flows/simple/agents/agent.md

@@ -119,6 +119,15 @@ On activation, read:
 specs/                               # Existing specs (for state detection)
 ```
 
+## Asking Questions
+
+When you need to ask the user a question (e.g., clarifying vague input), check for these tools:
+
+- `userInput` (Kiro)
+- `AskUserQuestionTool` (Claude Code)
+
+If either tool is available, use it to ask structured questions. If neither is available, ask directly in your response text.
+
 ## State Detection
 
 Check `specs/{feature-name}/` to determine state:

package/flows/simple/commands/agent.md

@@ -16,7 +16,7 @@ When this command is invoked, the agent should:
 1. **Load Context**
    - Read `.specsmd/simple/memory-bank.yaml`
    - Read `.specsmd/simple/agents/agent.md`
-   - Scan `memory-bank/specs/` for existing specs
+   - Scan `specs/` for existing specs
 
 2. **Parse Arguments**
    - `$ARGUMENTS` contains user input after command

package/flows/simple/context-config.yaml

@@ -16,19 +16,19 @@ context:
     design:
       - path: ".specsmd/simple/skills/design.md"
       - path: ".specsmd/simple/templates/design-template.md"
-      - path: "memory-bank/specs/{feature}/requirements.md"
+      - path: "specs/{feature}/requirements.md"
     tasks:
       - path: ".specsmd/simple/skills/tasks.md"
       - path: ".specsmd/simple/templates/tasks-template.md"
-      - path: "memory-bank/specs/{feature}/requirements.md"
-      - path: "memory-bank/specs/{feature}/design.md"
+      - path: "specs/{feature}/requirements.md"
+      - path: "specs/{feature}/design.md"
     execute:
       - path: ".specsmd/simple/skills/execute.md"
-      - path: "memory-bank/specs/{feature}/requirements.md"
-      - path: "memory-bank/specs/{feature}/design.md"
-      - path: "memory-bank/specs/{feature}/tasks.md"
+      - path: "specs/{feature}/requirements.md"
+      - path: "specs/{feature}/design.md"
+      - path: "specs/{feature}/tasks.md"
 
 # Scan directories on activation
 scan:
-  - path: "memory-bank/specs/"
+  - path: "specs/"
     purpose: "Detect existing specs for state detection"

package/flows/simple/memory-bank.yaml

@@ -27,10 +27,10 @@ naming:
 
 # Schema Definition (Source of Truth for Agent)
 schema:
-  specs: "memory-bank/specs/{feature-name}/"
-  requirements: "memory-bank/specs/{feature-name}/requirements.md"
-  design: "memory-bank/specs/{feature-name}/design.md"
-  tasks: "memory-bank/specs/{feature-name}/tasks.md"
+  specs: "specs/{feature-name}/"
+  requirements: "specs/{feature-name}/requirements.md"
+  design: "specs/{feature-name}/design.md"
+  tasks: "specs/{feature-name}/tasks.md"
 
 # Workflow Configuration
 workflow:

package/flows/simple/quick-start.md

@@ -126,12 +126,11 @@ After creating specs, your project will have:
     ├── memory-bank.yaml          # Storage schema
     └── quick-start.md            # This file
 
-memory-bank/
-└── specs/                        # Your feature specs
-    └── {feature-name}/
-        ├── requirements.md       # What to build
-        ├── design.md             # How to build it
-        └── tasks.md              # Step-by-step plan
+specs/                                # Your feature specs
+└── {feature-name}/
+    ├── requirements.md           # What to build
+    ├── design.md                 # How to build it
+    └── tasks.md                  # Step-by-step plan
 ```
 
 ---
@@ -190,7 +189,7 @@ The agent is stateless. It reads spec files at startup. Ensure documents are sav
 When you run `/specsmd-agent` without arguments, it lists existing specs and asks which to work on.
 
 ### Want to start over
-Delete the spec folder: `rm -rf memory-bank/specs/{feature-name}`
+Delete the spec folder: `rm -rf specs/{feature-name}`
 
 ### Get help
 Ask the agent: `/specsmd-agent How do I add a new requirement?`

package/flows/simple/skills/design.md

@@ -19,10 +19,10 @@ Generate a technical design document based on approved requirements. This is Pha
 
 ### Initial Generation
 
-1. **Read requirements** from `memory-bank/specs/{feature}/requirements.md`
+1. **Read requirements** from `specs/{feature}/requirements.md`
 2. **Research codebase** if needed:
    - Identify existing patterns and conventions
-   - Check tech stack from `memory-bank/standards/` if available
+   - Check existing project standards if available
    - Look for similar implementations to reference
 3. **Generate design.md** following the template:
    - Overview (solution approach, tech decisions)
@@ -31,7 +31,7 @@ Generate a technical design document based on approved requirements. This is Pha
    - Data Models (with validation rules)
    - Error Handling (recovery strategies)
    - Testing Strategy
-4. **Write file** to `memory-bank/specs/{feature}/design.md`
+4. **Write file** to `specs/{feature}/design.md`
 5. **Ask for approval**: "Does the design look good? If so, we can move on to the implementation plan."
 
 ### Update Flow
@@ -65,7 +65,7 @@ Generate a technical design document based on approved requirements. This is Pha
 
 ## Output
 
-- **File**: `memory-bank/specs/{feature-name}/design.md`
+- **File**: `specs/{feature-name}/design.md`
 - **Approval Prompt**: "Does the design look good? If so, we can move on to the implementation plan."
 
 ## Design Sections Checklist

package/flows/simple/skills/execute.md

@@ -7,9 +7,9 @@ Execute implementation tasks from an approved tasks.md file. This is the post-sp
 ## Preconditions
 
 - All three spec files exist:
-  - `memory-bank/specs/{feature}/requirements.md`
-  - `memory-bank/specs/{feature}/design.md`
-  - `memory-bank/specs/{feature}/tasks.md`
+  - `specs/{feature}/requirements.md`
+  - `specs/{feature}/design.md`
+  - `specs/{feature}/tasks.md`
 - Tasks have been approved by user
 
 ## Trigger Conditions

package/flows/simple/skills/requirements.md

@@ -16,12 +16,12 @@ Generate a requirements document for a feature using EARS (Easy Approach to Requ
 
 1. **Parse feature idea** from user input
 2. **Derive feature name** in kebab-case (e.g., "user-authentication")
-3. **Create directory** at `memory-bank/specs/{feature-name}/`
+3. **Create directory** at `specs/{feature-name}/`
 4. **Generate requirements.md** following the template:
    - Introduction (2-3 sentences)
    - Glossary (3-10 domain terms)
    - Requirements (3-7 user stories with EARS acceptance criteria)
-5. **Write file** to `memory-bank/specs/{feature-name}/requirements.md`
+5. **Write file** to `specs/{feature-name}/requirements.md`
 6. **Ask for approval**: "Do the requirements look good? If so, we can move on to the design."
 
 ### Update Flow (Existing Spec)
@@ -53,7 +53,7 @@ Generate a requirements document for a feature using EARS (Easy Approach to Requ
 
 ## Output
 
-- **File**: `memory-bank/specs/{feature-name}/requirements.md`
+- **File**: `specs/{feature-name}/requirements.md`
 - **Approval Prompt**: "Do the requirements look good? If so, we can move on to the design."
 
 ## Example Generation

package/flows/simple/skills/tasks.md

@@ -20,8 +20,8 @@ Generate an implementation plan with coding tasks based on the approved design.
 ### Initial Generation
 
 1. **Read both documents**:
-   - `memory-bank/specs/{feature}/requirements.md`
-   - `memory-bank/specs/{feature}/design.md`
+   - `specs/{feature}/requirements.md`
+   - `specs/{feature}/design.md`
 2. **Convert design into tasks**:
    - Create incremental coding steps
    - Each task builds on previous
@@ -31,7 +31,7 @@ Generate an implementation plan with coding tasks based on the approved design.
    - Numbered checkbox list
    - Max 2 levels of hierarchy
    - Requirement references for traceability
-4. **Write file** to `memory-bank/specs/{feature}/tasks.md`
+4. **Write file** to `specs/{feature}/tasks.md`
 5. **Ask for approval**: "Do the tasks look good?"
 
 ### Update Flow
@@ -82,7 +82,7 @@ Generate an implementation plan with coding tasks based on the approved design.
 
 ## Output
 
-- **File**: `memory-bank/specs/{feature-name}/tasks.md`
+- **File**: `specs/{feature-name}/tasks.md`
 - **Approval Prompt**: "Do the tasks look good?"
 
 ## Task Types (Include)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "specsmd",
-  "version": "0.0.0-dev.31",
+  "version": "0.0.0-dev.33",
   "description": "Multi-agent orchestration system for AI-native software development. Delivers AI-DLC, Agile, and custom SDLC flows as markdown-based agent systems.",
   "main": "lib/installer.js",
   "bin": {