fix: complete [n] → [NN] placeholder consistency across all prompt files

- Fixed remaining [n] placeholders in validate-spec-implementation.md
- Fixed [n] → [NN] in generate-spec.md template header
- Fixed [n] → [NN] in generate-task-list-from-spec.md final instructions
- Fixed [n] → [NN] in manage-tasks.md checklist and protocol sections
- All prompt files now consistently use [NN] for zero-padded two-digit spec numbers
- Quality gates pass: pre-commit hooks, linting, and formatting

Author: ryderstorm

prompts/generate-spec.md

@@ -155,7 +155,7 @@ If the feature involves existing systems, briefly review the codebase and existi
 Generate a comprehensive specification using this exact structure:
 
 ```markdown
-# [n]-spec-[feature-name].md
+# [NN]-spec-[feature-name].md
 
 ## Introduction/Overview
 

prompts/generate-task-list-from-spec.md

@@ -237,7 +237,7 @@ Once this task list is complete and approved, instruct the user to run `/manage-
 
 1. Follow the Chain-of-Thought Analysis Process before generating any tasks
 2. Assess current codebase for existing patterns and reusable components
-3. Generate high-level tasks that represent demoable units of work (adjust count based on spec complexity) and save them to `./docs/specs/[n]-spec-[feature-name]/[n]-tasks-[feature-name].md`
+3. Generate high-level tasks that represent demoable units of work (adjust count based on spec complexity) and save them to `./docs/specs/[NN]-spec-[feature-name]/[NN]-tasks-[feature-name].md`
 4. **CRITICAL**: Stop after generating parent tasks and wait for "Generate sub tasks" confirmation before proceeding.
 5. Ensure every parent task has specific Demo Criteria and Proof Artifacts
 6. Identify all relevant files for creation/modification

prompts/manage-tasks.md

@@ -80,7 +80,7 @@ For each parent task, follow this structured workflow with built-in verification
 ```markdown
 ## PRE-WORK CHECKLIST (Complete before starting any sub-task)
 
-[ ] Locate task file: `./docs/specs/[n]-spec-[feature-name]/[n]-tasks-[feature-name].md`
+[ ] Locate task file: `./docs/specs/[NN]-spec-[feature-name]/[NN]-tasks-[feature-name].md`
 [ ] Read current task status and identify next sub-task
 [ ] Verify checkpoint mode preference with user
 [ ] Confirm demo criteria for current parent task
@@ -206,7 +206,7 @@ Each parent task must include artifacts that:
 
 For each parent task completion:
 
-[ ] **Directory Ready**: `./docs/specs/[n]-spec-[feature-name]/[n]-proofs/` exists
+[ ] **Directory Ready**: `./docs/specs/[NN]-spec-[feature-name]/[NN]-proofs/` exists
 [ ] **Review Task Requirements**: Check what demo evidence the task specifically requires
 [ ] **Create Single Proof File**: Create `[spec-number]-task-[task-number]-proofs.md`
 [ ] **Include All Evidence in One File**:

prompts/validate-spec-implementation.md

@@ -60,8 +60,8 @@ Validate that the **code changes** conform to the Spec and Task List by verifyin
 
 If no spec is provided, follow this exact sequence:
 
-1. Scan `./docs/specs/` for directories matching pattern `[n]-spec-[feature-name]/`
-2. Identify spec directories with corresponding `[n]-tasks-[feature-name].md` files
+1. Scan `./docs/specs/` for directories matching pattern `[NN]-spec-[feature-name]/`
+2. Identify spec directories with corresponding `[NN]-tasks-[feature-name].md` files
 3. Select the spec with:
    - Highest sequence number where task list exists
    - At least one incomplete parent task (`[ ]` or `[~]`)