specsmd 0.0.34 → 0.1.1

package/flows/aidlc/skills/inception/bolt-plan.md

@@ -190,35 +190,51 @@ Establish execution order based on dependencies:
 1. **Read Path**: Check `schema.bolts` from `.specsmd/aidlc/memory-bank.yaml`
    *(Default: `memory-bank/bolts/{bolt-id}/`)*
 
-2. **Create Directory + File Per Bolt**:
+2. **Determine Bolt ID**:
+   - List all directories in `memory-bank/bolts/`
+   - Extract the 3-digit prefix from each (e.g., `015` from `015-auth-service`)
+   - Find the highest number
+   - Next bolt uses the next available number (e.g., if highest is `015`, next is `016`)
+
+   **⚠️ CRITICAL**: The `{BBB}` prefix is a **GLOBAL** sequence across ALL bolts in `memory-bank/bolts/`, NOT per-unit.
+
+3. **Create Directory + File Per Bolt**:
    For EACH bolt in the plan:
-   - Create directory: `memory-bank/bolts/bolt-{unit}-{N}/`
-   - Create file inside: `memory-bank/bolts/bolt-{unit}-{N}/bolt.md`
+   - Create directory: `memory-bank/bolts/{BBB}-{unit-name}/`
+   - Create file inside: `memory-bank/bolts/{BBB}-{unit-name}/bolt.md`
    - Use template: `.specsmd/aidlc/templates/construction/bolt-template.md`
 
-   **Example**: If planning 3 bolts for auth unit, CREATE THESE:
+   **Naming Convention** (from `memory-bank.yaml`):
+   - Format: `{BBB}-{unit-name}/` where BBB is a **GLOBAL** 3-digit sequence
+   - The number is global across ALL bolts in `memory-bank/bolts/` (not per-unit)
+   - Example sequence: `001-auth-service/`, `002-auth-service/`, `003-payment-service/`, `004-auth-service/`
+
+   **Example**: Planning bolts across multiple units (global numbering):
 
    ```text
-   memory-bank/bolts/bolt-auth-1/bolt.md  ← CREATE THIS DIRECTORY AND FILE
-   memory-bank/bolts/bolt-auth-2/bolt.md  ← CREATE THIS DIRECTORY AND FILE
-   memory-bank/bolts/bolt-auth-3/bolt.md  ← CREATE THIS DIRECTORY AND FILE
+   memory-bank/bolts/
+   ├── 001-auth-service/bolt.md     ← First bolt ever created
+   ├── 002-auth-service/bolt.md     ← Second bolt (same unit, continues sequence)
+   ├── 003-payment-service/bolt.md  ← Third bolt (different unit)
+   ├── 004-auth-service/bolt.md     ← Fourth bolt (back to auth-service)
+   └── 005-api-gateway/bolt.md      ← Fifth bolt (another unit)
    ```
 
    **Stage artifacts will be added to same directory during construction:**
 
    ```text
-   memory-bank/bolts/bolt-auth-1/
+   memory-bank/bolts/001-auth-service/
    ├── bolt.md                      ← You create this now
    └── {stage-artifacts}            ← Created during construction (varies by bolt type)
    ```
 
-   *Note: Artifact names depend on bolt type (e.g., DDD bolts create `ddd-01-domain-model.md`, simple bolts create `spec.md`).*
+   *Note: Artifact names depend on bolt type (e.g., DDD bolts create `ddd-01-domain-model.md`, simple bolts create `implementation-plan.md`).*
 
-3. **Bolt File Structure** (CRITICAL: Include all dependencies in frontmatter):
+4. **Bolt File Structure** (CRITICAL: Include all dependencies in frontmatter):
 
    ```markdown
    ---
-   id: bolt-{unit}-{sequence}
+   id: {BBB}-{unit-name}
    unit: {unit-name}
    intent: {intent-name}
    type: {bolt-type}  # From unit-brief.md or default (ddd-construction-bolt, simple-construction-bolt)
@@ -227,8 +243,8 @@ Establish execution order based on dependencies:
    created: {date}
 
    # Dependency Tracking (REQUIRED)
-   requires_bolts: [bolt-auth-1]           # Bolts that must complete first
-   enables_bolts: [bolt-auth-3, bolt-api-1] # Bolts that depend on this
+   requires_bolts: [001-auth-service]       # Bolts that must complete first
+   enables_bolts: [003-auth-service, 001-api-service] # Bolts that depend on this
    requires_units: [auth-service]           # Units that must be complete
    blocks: false                            # true if waiting on dependency
 
@@ -240,7 +256,7 @@ Establish execution order based on dependencies:
      testing_scope: 2         # 1=Unit, 2=Integration, 3=E2E
    ---
 
-   ## Bolt: {bolt-id}
+   ## Bolt: {BBB}-{unit-name}
 
    ### Objective
    {What this bolt will accomplish}
@@ -257,19 +273,19 @@ Establish execution order based on dependencies:
 
    #### Bolt Dependencies (within intent)
 
-   - **bolt-auth-1** (Required): Completed
-   - **bolt-auth-2** (Optional): In Progress
+   - **001-auth-service** (Required): Completed
+   - **002-auth-service** (Optional): In Progress
 
    #### Unit Dependencies (cross-unit)
 
    - **auth-service**: Needs auth tokens - Completed
 
    #### Enables (other bolts waiting on this)
-   - bolt-auth-3
-   - bolt-api-1
+   - 003-auth-service
+   - 001-api-service
    ```
 
-### 8. Validate Plan
+### 9. Validate Plan
 
 Check the plan against:
 
@@ -291,16 +307,20 @@ Check the plan against:
 **⚠️ YOU MUST CREATE THESE DIRECTORIES AND FILES:**
 
 ```text
-memory-bank/bolts/bolt-{unit}-1/bolt.md  ← CREATE THIS DIRECTORY AND FILE
-memory-bank/bolts/bolt-{unit}-2/bolt.md  ← CREATE THIS DIRECTORY AND FILE
-memory-bank/bolts/bolt-{unit}-3/bolt.md  ← CREATE THIS DIRECTORY AND FILE
+memory-bank/bolts/{BBB}-{unit-name}/bolt.md  ← CREATE THIS DIRECTORY AND FILE
 ```
 
+**Naming Convention** (from `memory-bank.yaml`):
+
+- Format: `{BBB}-{unit-name}/` where BBB is a global 3-digit sequence
+- Example: `001-auth-service/`, `002-auth-service/`, `016-analytics-tracker/`
+
 **⚠️ DO NOT CREATE:**
 
 - `bolt-plan.md` (summary doc)
 - `README.md` files
-- Flat files like `bolt-{unit}-1.md`
+- Flat files like `001-auth-service.md` (must be in directory)
+- Old format like `bolt-{unit}-1/` (incorrect)
 
 ### Summary (displayed to user)
 
@@ -309,17 +329,17 @@ memory-bank/bolts/bolt-{unit}-3/bolt.md  ← CREATE THIS DIRECTORY AND FILE
 
 ### Bolts Created
 
-- [ ] **bolt-{unit}-1** ({bolt-type}): 001-user-signup, 002-user-login
-- [ ] **bolt-{unit}-2** ({bolt-type}): 003-password-reset, 004-email-verify
-- [ ] **bolt-{unit}-3** ({bolt-type}): 005-mfa-setup
+- [ ] **001-auth-service** ({bolt-type}): 001-user-signup, 002-user-login
+- [ ] **002-auth-service** ({bolt-type}): 003-password-reset, 004-email-verify
+- [ ] **003-auth-service** ({bolt-type}): 005-mfa-setup
 
 ### Dependency Graph
-bolt-{unit}-1 ──► bolt-{unit}-2 ──► bolt-{unit}-3
+001-auth-service ──► 002-auth-service ──► 003-auth-service
 
 ### Directories Created
-✅ `memory-bank/bolts/bolt-{unit}-1/bolt.md`
-✅ `memory-bank/bolts/bolt-{unit}-2/bolt.md`
-✅ `memory-bank/bolts/bolt-{unit}-3/bolt.md`
+✅ `memory-bank/bolts/001-auth-service/bolt.md`
+✅ `memory-bank/bolts/002-auth-service/bolt.md`
+✅ `memory-bank/bolts/003-auth-service/bolt.md`
 
 ### Total
 - {n} bolts created

package/flows/aidlc/skills/master/analyze-context.md

@@ -70,6 +70,106 @@ Based on evidence found:
 - **All bolts completed** → Ready for Operations → Deploy unit
 - **Deployed to production** → Operations → Monitor and maintain
 
+### 6. Validate Status Integrity
+
+Check for status inconsistencies across the artifact hierarchy. Status must cascade correctly:
+
+```text
+Bolt complete → Stories complete → Unit complete (if all bolts done) → Intent complete (if all units done)
+```
+
+#### 6.1 Story Status Check
+
+For each completed bolt:
+
+- Read bolt's `stories` array
+- Check each story file's `status` field
+- **Inconsistency**: Bolt complete but story has `status: draft` or `status: in-progress`
+
+#### 6.2 Unit Status Check
+
+For each unit:
+
+- Find all bolts for unit: `memory-bank/bolts/bolt-{unit}-*/bolt.md`
+- Determine expected status:
+  - If ANY bolt `in-progress` → unit should be `in-progress`
+  - If ALL bolts `complete` → unit should be `complete`
+  - If ALL bolts `planned` and at least one story defined → unit should be `stories-defined`
+  - If NO bolts exist but stories exist → unit should be `stories-defined`
+- **Inconsistency**: Unit status doesn't match expected based on bolt states
+
+#### 6.3 Intent Status Check
+
+For each intent:
+
+- Read all unit-briefs: `{intent}/units/*/unit-brief.md`
+- Determine expected status:
+  - If ANY unit `in-progress` → intent should be `construction`
+  - If ALL units `complete` → intent should be `complete`
+  - If units defined but none started → intent should be `units-defined`
+- **Inconsistency**: Intent status doesn't match expected based on unit states
+
+#### 6.4 Report Inconsistencies
+
+If inconsistencies found, report them:
+
+```markdown
+## ⚠️ Status Inconsistencies Detected
+
+| Artifact | Current Status | Expected Status | Reason |
+|----------|----------------|-----------------|--------|
+| unit-brief: file-watcher | draft | complete | All bolts complete |
+| requirements: 011-vscode-extension | units-defined | construction | Has in-progress units |
+
+### Actions
+1 - **fix**: Update all statuses to expected values
+2 - **skip**: Continue without fixing
+3 - **review**: Show details for each inconsistency
+
+**Type 1 to fix inconsistencies, or 2 to skip.**
+```
+
+#### 6.5 Auto-Fix (On User Confirmation)
+
+If user confirms fix:
+
+- Update each artifact's frontmatter `status` field
+- Update `updated` timestamp to current date
+- Log changes to `memory-bank/maintenance-log.md`
+- Report changes made
+
+#### 6.6 Log to Maintenance Log
+
+Append entry to `memory-bank/maintenance-log.md` (create if doesn't exist):
+
+```markdown
+## {ISO-8601-timestamp} - Status Sync
+
+**Triggered by**: analyze-context integrity check
+
+| Artifact | Old Status | New Status | Reason |
+|----------|------------|------------|--------|
+| {path} | {old} | {new} | {reason} |
+
+---
+```
+
+**Example**:
+
+```markdown
+## 2025-12-26T15:30:00Z - Status Sync
+
+**Triggered by**: analyze-context integrity check
+
+| Artifact | Old Status | New Status | Reason |
+|----------|------------|------------|--------|
+| 011-vscode-extension/units/file-watcher/unit-brief.md | draft | complete | All bolts complete (1/1) |
+| 011-vscode-extension/units/extension-core/unit-brief.md | draft | complete | All bolts complete (1/1) |
+| 011-vscode-extension/requirements.md | units-defined | construction | Has in-progress units |
+
+---
+```
+
 ---
 
 ## Output
@@ -91,14 +191,21 @@ Provide a structured analysis:
 - Stories found: {count} for {unit}
 - Bolts found: {count} ({status breakdown})
 
+### Status Integrity
+- ✅ All statuses consistent (or)
+- ⚠️ {N} inconsistencies found (see details below)
+
 ### Current State Details
 {Specific details about what exists and what's missing}
 
+{If inconsistencies found, include the inconsistency table here}
+
 ### Actions
 
 1 - **proceed**: Execute suggested action
 2 - **explain**: Learn more about current phase
 3 - **different**: Work on something else
+{If inconsistencies: 4 - **fix**: Fix status inconsistencies}
 
 ### Suggested Next Step
 → **proceed** - {Specific command to run}

package/flows/aidlc/skills/master/explain-flow.md

@@ -41,11 +41,23 @@ AI-DLC is a reimagined development methodology where AI drives the workflow and
    - Output: Complete implementation plan
 
 2. **Construction** → Building & Testing
-   - Execute bolts through their stages
+   - Execute bolts through their stages (stages vary by bolt type)
    - AI generates designs, code, and tests
    - Human validates at each stage
    - Output: Tested, working code
 
+   **DDD Bolt** (for domain-heavy business logic):
+   - Stage 1: Domain Model → AI models entities, aggregates, events
+   - Stage 2: Technical Design → AI architects layers, APIs, data
+   - Stage 3: ADR Analysis → Capture architectural decisions (optional)
+   - Stage 4: Implement → AI generates code from designs
+   - Stage 5: Test → AI writes and runs tests
+
+   **Simple Bolt** (for straightforward tasks):
+   - Stage 1: Plan → Define what to build
+   - Stage 2: Implement → AI generates code
+   - Stage 3: Test → AI writes and runs tests
+
 3. **Operations** → Deploy & Monitor
    - Package deployment units
    - Deploy through environments (Dev → Staging → Prod)

package/flows/aidlc/templates/construction/bolt-template.md

@@ -34,12 +34,18 @@ status: planned
 stories:
   - story-1
   - story-2
-created: {YYYY-MM-DD}
+created: {YYYY-MM-DDTHH:MM:SSZ}
 started: null
 completed: null
 current_stage: null
 stages_completed: []
 
+# Bolt Dependencies (for execution ordering)
+requires_bolts: []          # Bolts that must complete before this bolt can start
+enables_bolts: []           # Bolts that become unblocked when this bolt completes
+requires_units: []          # Units that must exist (usually empty)
+blocks: false               # Computed: true if any requires_bolts are incomplete
+
 # Complexity Assessment (aggregate of included stories)
 complexity:
   avg_complexity: 2        # 1=Low, 2=Medium, 3=High
@@ -142,6 +148,12 @@ stages_completed:
     completed: 2024-12-05T10:00:00Z
     artifact: ddd-01-domain-model.md
 
+requires_bolts: []
+enables_bolts:
+  - bolt-auth-service-2
+requires_units: []
+blocks: false
+
 complexity:
   avg_complexity: 2
   avg_uncertainty: 1

package/flows/aidlc/templates/construction/bolt-types/ddd-construction-bolt/adr-template.md

@@ -1,6 +1,6 @@
 ---
 bolt: {bolt-id}
-created: {timestamp}
+created: {YYYY-MM-DDTHH:MM:SSZ}
 status: proposed | accepted | deprecated | superseded
 superseded_by: {adr-number if applicable}
 ---

package/flows/aidlc/templates/construction/bolt-types/ddd-construction-bolt/ddd-01-domain-model-template.md

@@ -3,7 +3,7 @@ unit: {unit-name}
 bolt: {bolt-id}
 stage: model
 status: complete
-updated: {date}
+updated: {YYYY-MM-DDTHH:MM:SSZ}
 ---
 
 # Static Model - {Unit Name}

package/flows/aidlc/templates/construction/bolt-types/ddd-construction-bolt/ddd-02-technical-design-template.md

@@ -3,7 +3,7 @@ unit: {unit-name}
 bolt: {bolt-id}
 stage: design
 status: complete
-updated: {date}
+updated: {YYYY-MM-DDTHH:MM:SSZ}
 ---
 
 # Technical Design - {Unit Name}

package/flows/aidlc/templates/construction/bolt-types/ddd-construction-bolt/ddd-03-test-report-template.md

@@ -3,7 +3,7 @@ unit: {unit-name}
 bolt: {bolt-id}
 stage: test
 status: complete
-updated: {date}
+updated: {YYYY-MM-DDTHH:MM:SSZ}
 ---
 
 # Test Report - {Unit Name}

package/flows/aidlc/templates/construction/bolt-types/ddd-construction-bolt.md

@@ -109,7 +109,7 @@ This bolt type implements Domain-Driven Design (DDD) methodology through five se
 ---
 stage: model
 bolt: {bolt-id}
-created: {timestamp}
+created: {YYYY-MM-DDTHH:MM:SSZ}
 ---
 
 ## Static Model: {unit-name}
@@ -189,7 +189,7 @@ created: {timestamp}
 ---
 stage: design
 bolt: {bolt-id}
-created: {timestamp}
+created: {YYYY-MM-DDTHH:MM:SSZ}
 ---
 
 ## Technical Design: {unit-name}
@@ -440,7 +440,7 @@ tests/
 ---
 stage: test
 bolt: {bolt-id}
-created: {timestamp}
+created: {YYYY-MM-DDTHH:MM:SSZ}
 ---
 
 ## Test Report: {unit-name}

package/flows/aidlc/templates/construction/bolt-types/simple-construction-bolt.md

@@ -25,14 +25,14 @@
 **Stages MUST be executed in this exact order:**
 
 ```text
-Stage 1: Spec → Stage 2: Implement → Stage 3: Test
+Stage 1: Plan → Stage 2: Implement → Stage 3: Test
 ```
 
 **Stage Overview:**
 
-- ✅/[ ] **1. Spec** (Required) → `spec.md`
-- ✅/[ ] **2. Implement** (Required) → Source code
-- ✅/[ ] **3. Test** (Required) → Tests + `test-report.md`
+- ✅/[ ] **1. Plan** (Required) → `implementation-plan.md`
+- ✅/[ ] **2. Implement** (Required) → Source code + `implementation-walkthrough.md`
+- ✅/[ ] **3. Test** (Required) → Tests + `test-walkthrough.md`
 
 **Rules**:
 
@@ -84,7 +84,7 @@ This bolt type provides a lightweight construction process for work that doesn't
 
 ## Stages
 
-### Stage 1: Spec
+### Stage 1: Plan
 
 **Objective**: Define what to build with clear requirements
 
@@ -98,19 +98,19 @@ This bolt type provides a lightweight construction process for work that doesn't
 4 - **Define acceptance criteria**: How will we know it's done?
 5 - **Note technical approach**: High-level implementation notes
 
-**Artifact**: `spec.md`
-**Location**: `memory-bank/bolts/{bolt-id}/spec.md`
+**Artifact**: `implementation-plan.md`
+**Location**: `memory-bank/bolts/{bolt-id}/implementation-plan.md`
 
 **Template Structure**:
 
 ```markdown
 ---
-stage: spec
+stage: plan
 bolt: {bolt-id}
-created: {timestamp}
+created: {YYYY-MM-DDTHH:MM:SSZ}
 ---
 
-## Spec: {unit-name}
+## Implementation Plan: {unit-name}
 
 ### Objective
 {What this bolt will accomplish}
@@ -137,13 +137,13 @@ created: {timestamp}
 - [ ] Dependencies identified
 - [ ] Acceptance criteria documented
 
-**⛔ HUMAN Checkpoint**: Present spec summary and **STOP**. Wait for user to confirm before proceeding to Stage 2.
+**⛔ HUMAN Checkpoint**: Present plan summary and **STOP**. Wait for user to confirm before proceeding to Stage 2.
 
 ---
 
 ### Stage 2: Implement
 
-**Objective**: Write the code
+**Objective**: Write the code and document what was done
 
 **Duration**: Hours (varies by complexity)
 
@@ -154,16 +154,84 @@ created: {timestamp}
 3 - **Handle edge cases**: Error handling, validation
 4 - **Add documentation**: Code comments, JSDoc/docstrings
 5 - **Run linting**: Ensure code style compliance
+6 - **Document implementation**: Create implementation walkthrough
 
-**Artifact**: Source code
-**Location**: As defined in project structure (e.g., `src/`, `app/`, `pages/`)
+**Artifacts**:
+
+- Source code - As defined in project structure (e.g., `src/`, `app/`, `pages/`)
+- `implementation-walkthrough.md` - `memory-bank/bolts/{bolt-id}/implementation-walkthrough.md`
+
+**Implementation Walkthrough Guidelines**:
+
+⚠️ **CRITICAL RULES**:
+
+- **NO CODE** in this document - only structure summaries and descriptions
+- **USE CHECKMARKS** for all file entries (completed work)
+- **BE CONSISTENT** - follow the template exactly
+
+**Template**:
+
+```markdown
+---
+stage: implement
+bolt: {bolt-id}
+created: {YYYY-MM-DDTHH:MM:SSZ}
+---
+
+## Implementation Walkthrough: {unit-name}
+
+### Summary
+
+{2-3 sentence overview of what was built - NO CODE}
+
+### Structure Overview
+
+{High-level description of the architecture/organization - NO CODE}
+
+### Completed Work
+
+- [x] `{path/to/file}` - {what this file does, not how}
+- [x] `{path/to/file}` - {what this file does, not how}
+- [x] `{path/to/file}` - {what this file does, not how}
+
+### Key Decisions
+
+- **{Decision}**: {Why this approach was chosen}
+
+### Deviations from Plan
+
+{Any changes from implementation-plan.md and why, or "None"}
+
+### Dependencies Added
+
+- [x] `{package}` - {why needed}
+
+### Developer Notes
+
+{Gotchas, tips, or context for future work - keep brief}
+```
+
+**What to Include**:
+
+- ✅ File paths with brief purpose descriptions
+- ✅ Architectural decisions and rationale
+- ✅ Deviations from original plan
+- ✅ High-level structure explanations
+
+**What NOT to Include**:
+
+- ❌ Code snippets or examples
+- ❌ Implementation details (how it works internally)
+- ❌ Line-by-line explanations
+- ❌ API signatures or type definitions
 
 **Completion Criteria**:
 
-- [ ] All deliverables from spec implemented
+- [ ] All deliverables from plan implemented
 - [ ] Code follows project coding standards
 - [ ] Linting passes
 - [ ] Code is documented
+- [ ] Implementation walkthrough created
 
 **⛔ HUMAN Checkpoint**: Present implementation summary and **STOP**. Wait for user to confirm before proceeding to Stage 3.
 
@@ -180,11 +248,11 @@ created: {timestamp}
 1 - **Write unit tests**: Test individual functions/components
 2 - **Write integration tests**: Test API endpoints or component interactions
 3 - **Run test suite**: Execute all tests
-4 - **Verify acceptance criteria**: Check against spec
+4 - **Verify acceptance criteria**: Check against plan
 5 - **Document results**: Create test report
 
-**Artifact**: `test-report.md`
-**Location**: `memory-bank/bolts/{bolt-id}/test-report.md`
+**Artifact**: `test-walkthrough.md`
+**Location**: `memory-bank/bolts/{bolt-id}/test-walkthrough.md`
 
 **Template Structure**:
 
@@ -192,7 +260,7 @@ created: {timestamp}
 ---
 stage: test
 bolt: {bolt-id}
-created: {timestamp}
+created: {YYYY-MM-DDTHH:MM:SSZ}
 ---
 
 ## Test Report: {unit-name}
@@ -231,9 +299,9 @@ Bolt instance tracks progress:
 ---
 current_stage: implement
 stages_completed:
-  - name: spec
+  - name: plan
     completed: 2024-12-05T10:00:00Z
-    artifact: spec.md
+    artifact: implementation-plan.md
 status: in-progress
 ---
 ```
@@ -249,9 +317,10 @@ For Stage 2 (Implement) and Stage 3 (Test), load all artifacts from the bolt fol
 **Load all files in this folder**, which may include:
 
 - `bolt.md` - Bolt instance metadata
-- `spec.md` - Spec from Stage 1
+- `implementation-plan.md` - Plan from Stage 1
+- `implementation-walkthrough.md` - Developer notes from Stage 2 (if exists)
 
-This ensures implementation and test stages have context from the spec.
+This ensures later stages have full context from earlier work.
 
 ---
 

package/flows/aidlc/templates/construction/bolt-types/spike-bolt.md

@@ -80,7 +80,7 @@ This bolt type is for research and proof-of-concept work when there are unknowns
 ---
 stage: explore
 bolt: {bolt-id}
-created: {timestamp}
+created: {YYYY-MM-DDTHH:MM:SSZ}
 time_box: {hours}
 ---
 
@@ -142,7 +142,7 @@ time_box: {hours}
 ---
 stage: document
 bolt: {bolt-id}
-created: {timestamp}
+created: {YYYY-MM-DDTHH:MM:SSZ}
 ---
 
 ## Spike Report: {topic}

package/flows/aidlc/templates/construction/construction-log-template.md

@@ -16,8 +16,8 @@ Use this template to track construction progress and replanning decisions for a
 ---
 unit: {unit-name}
 intent: {intent-name}
-created: {YYYY-MM-DD}
-last_updated: {YYYY-MM-DD}
+created: {YYYY-MM-DDTHH:MM:SSZ}
+last_updated: {YYYY-MM-DDTHH:MM:SSZ}
 ---
 
 # Construction Log: {unit-name}

package/flows/aidlc/templates/inception/inception-log-template.md

@@ -15,8 +15,8 @@ Use this template to track inception progress and decisions for an intent.
 ```markdown
 ---
 intent: {intent-name}
-created: {YYYY-MM-DD}
-completed: {YYYY-MM-DD or null}
+created: {YYYY-MM-DDTHH:MM:SSZ}
+completed: {YYYY-MM-DDTHH:MM:SSZ or null}
 status: {in-progress | complete}
 ---
 

package/flows/aidlc/templates/inception/requirements-template.md

@@ -11,8 +11,8 @@ Use this template when documenting requirements for an intent.
 intent: {intent-name}
 phase: inception
 status: draft|in-progress|complete
-created: {YYYY-MM-DD}
-updated: {YYYY-MM-DD}
+created: {YYYY-MM-DDTHH:MM:SSZ}
+updated: {YYYY-MM-DDTHH:MM:SSZ}
 ---
 ```
 

package/flows/aidlc/templates/inception/stories-template.md

@@ -2,7 +2,7 @@
 intent: {intent-name}
 phase: inception
 status: stories-created
-updated: {date}
+updated: {YYYY-MM-DDTHH:MM:SSZ}
 ---
 
 # {Intent Name} - Stories