red64-cli 0.2.0 → 0.5.0

package/framework/agents/codex/.codex/agents/red64/validate-gap.md

@@ -1,7 +1,7 @@
 ---
 name: validate-gap-agent
 description: Analyze implementation gap between requirements and existing codebase
-tools: Read, Grep, Glob, WebSearch, WebFetch
+tools: Read, Write, Edit, Grep, Glob, WebSearch, WebFetch
 model: inherit
 color: yellow
 ---
@@ -49,6 +49,7 @@ Analyze implementation gap for feature based on approved requirements and existi
 
 2. **Read Analysis Guidelines**:
    - Read `.red64/settings/rules/gap-analysis.md` for comprehensive analysis framework
+   - Read `.red64/settings/templates/specs/gap-analysis.md` for document structure
 
 3. **Execute Gap Analysis**:
    - Follow gap-analysis.md framework for thorough investigation
@@ -57,11 +58,15 @@ Analyze implementation gap for feature based on approved requirements and existi
    - Evaluate multiple implementation approaches (extend/new/hybrid)
    - Use language specified in spec.json for output
 
-4. **Generate Analysis Document**:
-   - Create comprehensive gap analysis following the output guidelines in gap-analysis.md
+4. **Write Analysis Document**:
+   - **Write gap analysis to `.red64/specs/{feature}/gap-analysis.md`** using the template structure
+   - Include: Requirement-to-Asset Map, Options A/B/C, Effort/Risk assessments, Recommendations
    - Present multiple viable options with trade-offs
    - Flag areas requiring further research
 
+5. **Update Metadata**:
+   - Edit `.red64/specs/{feature}/spec.json` to set `phase: "gap-analyzed"` if needed
+
 ## Important Constraints
 - **Information over Decisions**: Provide analysis and options, not final implementation choices
 - **Multiple Options**: Present viable alternatives when applicable
@@ -69,22 +74,23 @@ Analyze implementation gap for feature based on approved requirements and existi
 - **Explicit Gaps**: Clearly flag areas needing research or investigation
 
 ## Tool Guidance
-- **Read first**: Load all context (spec, steering, rules) before analysis
+- **Read first**: Load all context (spec, steering, rules, templates) before analysis
 - **Grep extensively**: Search codebase for patterns, conventions, and integration points
 - **WebSearch/WebFetch**: Research external dependencies and best practices when needed
-- **Write last**: Generate analysis only after complete investigation
+- **Write last**: Write gap-analysis.md only after complete investigation
 
 ## Output Description
 Provide output in the language specified in spec.json with:
 
 1. **Analysis Summary**: Brief overview (3-5 bullets) of scope, challenges, and recommendations
-2. **Document Status**: Confirm analysis approach used
+2. **Document Status**: Confirm gap-analysis.md was created at `.red64/specs/{feature}/gap-analysis.md`
 3. **Next Steps**: Guide user on proceeding to design phase
 
 **Format Requirements**:
 - Use Markdown headings for clarity
 - Keep summary concise (under 300 words)
-- Detailed analysis follows gap-analysis.md output guidelines
+- Include the full path to the generated gap-analysis.md file
+- Detailed analysis is in the generated document
 
 ## Safety & Fallback
 

package/framework/agents/codex/.codex/commands/red64/validate-gap.md

@@ -35,6 +35,10 @@ File patterns to read:
 - .red64/specs/$1/requirements.md
 - .red64/steering/*.md
 - .red64/settings/rules/gap-analysis.md
+- .red64/settings/templates/specs/gap-analysis.md
+
+Output:
+- Write gap analysis document to: .red64/specs/$1/gap-analysis.md
 """
 )
 ```

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "red64-cli",
-  "version": "0.2.0",
+  "version": "0.5.0",
   "description": "Red64 Flow Orchestrator - Deterministic spec-driven development CLI",
   "type": "module",
   "bin": {