create-claude-context 1.0.0 → 1.2.0

package/templates/base/commands/rpi-implement.md

@@ -1,115 +1,115 @@
----
-name: rpi-implement
-version: "1.0.0"
-description: "RPI Implement Phase: Execute plan with atomic changes and continuous testing"
-category: "rpi-orchestration"
-rpi_phase: "implement"
-context_budget_estimate: "60K tokens"
-typical_context_usage: "30%"
-prerequisites:
-  - "Plan document exists in .claude/plans/active/"
-  - "Plan has been approved by human"
-  - "Git branch is clean"
-  - "All tests currently passing"
-outputs:
-  - "Implemented feature/fix"
-  - "Updated documentation with new line numbers"
-  - "Commits with descriptive messages"
-  - "Archived plan in .claude/plans/completed/"
-next_commands: ["/verify-docs-current", "/validate-all"]
-related_agents: ["core-architect", "database-ops", "api-developer", "deployment-ops"]
-examples:
-  - command: "/rpi-implement user-authentication"
-    description: "Execute the approved authentication plan"
-  - command: "/rpi-implement payment-bug-fix"
-    description: "Implement the approved bug fix"
-exit_criteria:
-  - "All plan steps completed"
-  - "All tests passing"
-  - "Documentation updated"
-  - "Changes committed"
-  - "Plan archived to completed/"
----
-
-# RPI Implement Phase
-
-**Purpose:** Execute implementation plan atomically
-
-**Syntax:** `/rpi-implement [feature-name]`
-
-**Prerequisites:** Plan must be approved in `.claude/plans/active/`
-
----
-
-## Golden Rule
-
-```
-ONE CHANGE → ONE TEST → ONE COMMIT
-```
-
----
-
-## Execution Steps
-
-### Step 1: Load Plan
-Read `.claude/plans/active/[feature]_plan.md`
-
-### Step 2: Verify Preconditions
-- [ ] Plan is approved
-- [ ] Branch is clean
-- [ ] Tests pass before changes
-
-### Step 3: Execute Each Step
-For each step in plan:
-1. Make the single, atomic change
-2. Run step-specific test
-3. If pass: commit with descriptive message
-4. If fail: stop, investigate, do not proceed
-
-### Step 4: Context Reset (Every 3 Steps)
-1. Update progress in plan
-2. Re-read plan document
-3. Verify scope alignment
-4. Compact if >35% context usage
-
-### Step 5: Run Full Test Suite
-After all steps complete
-
-### Step 6: Update Documentation (MANDATORY)
-1. Check CODE_TO_WORKFLOW_MAP.md
-2. Update affected workflow files
-3. Update line numbers
-4. Run /verify-docs-current
-
-### Step 7: Final Commit
-Documentation updates
-
-### Step 8: Archive Plan
-Move to `.claude/plans/completed/`
-
----
-
-## Error Recovery
-
-| Error Type | Action |
-|------------|--------|
-| Syntax Error | Fix immediately |
-| Test Failure | Stop, investigate |
-| 3+ Failures | Compact, start new session |
-
----
-
-## Context Budget
-
-- Plan: 15k tokens
-- Active code: 30k tokens
-- Test results: 15k tokens
-- Total: 60k tokens (30%)
-
----
-
-## Output
-
-- Completed feature/fix
-- Updated documentation
-- Plan archived to completed/
+---
+name: rpi-implement
+version: "1.0.0"
+description: "RPI Implement Phase: Execute plan with atomic changes and continuous testing"
+category: "rpi-orchestration"
+rpi_phase: "implement"
+context_budget_estimate: "60K tokens"
+typical_context_usage: "30%"
+prerequisites:
+  - "Plan document exists in .claude/plans/active/"
+  - "Plan has been approved by human"
+  - "Git branch is clean"
+  - "All tests currently passing"
+outputs:
+  - "Implemented feature/fix"
+  - "Updated documentation with new line numbers"
+  - "Commits with descriptive messages"
+  - "Archived plan in .claude/plans/completed/"
+next_commands: ["/verify-docs-current", "/validate-all"]
+related_agents: ["core-architect", "database-ops", "api-developer", "deployment-ops"]
+examples:
+  - command: "/rpi-implement user-authentication"
+    description: "Execute the approved authentication plan"
+  - command: "/rpi-implement payment-bug-fix"
+    description: "Implement the approved bug fix"
+exit_criteria:
+  - "All plan steps completed"
+  - "All tests passing"
+  - "Documentation updated"
+  - "Changes committed"
+  - "Plan archived to completed/"
+---
+
+# RPI Implement Phase
+
+**Purpose:** Execute implementation plan atomically
+
+**Syntax:** `/rpi-implement [feature-name]`
+
+**Prerequisites:** Plan must be approved in `.claude/plans/active/`
+
+---
+
+## Golden Rule
+
+```
+ONE CHANGE → ONE TEST → ONE COMMIT
+```
+
+---
+
+## Execution Steps
+
+### Step 1: Load Plan
+Read `.claude/plans/active/[feature]_plan.md`
+
+### Step 2: Verify Preconditions
+- [ ] Plan is approved
+- [ ] Branch is clean
+- [ ] Tests pass before changes
+
+### Step 3: Execute Each Step
+For each step in plan:
+1. Make the single, atomic change
+2. Run step-specific test
+3. If pass: commit with descriptive message
+4. If fail: stop, investigate, do not proceed
+
+### Step 4: Context Reset (Every 3 Steps)
+1. Update progress in plan
+2. Re-read plan document
+3. Verify scope alignment
+4. Compact if >35% context usage
+
+### Step 5: Run Full Test Suite
+After all steps complete
+
+### Step 6: Update Documentation (MANDATORY)
+1. Check CODE_TO_WORKFLOW_MAP.md
+2. Update affected workflow files
+3. Update line numbers
+4. Run /verify-docs-current
+
+### Step 7: Final Commit
+Documentation updates
+
+### Step 8: Archive Plan
+Move to `.claude/plans/completed/`
+
+---
+
+## Error Recovery
+
+| Error Type | Action |
+|------------|--------|
+| Syntax Error | Fix immediately |
+| Test Failure | Stop, investigate |
+| 3+ Failures | Compact, start new session |
+
+---
+
+## Context Budget
+
+- Plan: 15k tokens
+- Active code: 30k tokens
+- Test results: 15k tokens
+- Total: 60k tokens (30%)
+
+---
+
+## Output
+
+- Completed feature/fix
+- Updated documentation
+- Plan archived to completed/

package/templates/base/commands/rpi-plan.md

@@ -1,93 +1,93 @@
----
-name: rpi-plan
-version: "1.0.0"
-description: "RPI Plan Phase: Create implementation blueprint with file:line precision"
-category: "rpi-orchestration"
-rpi_phase: "plan"
-context_budget_estimate: "35K tokens"
-typical_context_usage: "17%"
-prerequisites:
-  - "Research document exists in .claude/research/active/"
-  - "/rpi-research phase completed"
-outputs:
-  - "Plan document in .claude/plans/active/[name]_plan.md"
-  - "Modification table with file:line references"
-  - "Step-by-step implementation guide"
-  - "Test strategy"
-  - "Rollback plan"
-next_commands: ["/rpi-implement"]
-related_agents: ["core-architect", "database-ops", "api-developer"]
-examples:
-  - command: "/rpi-plan user-authentication"
-    description: "Create implementation plan for auth feature"
-  - command: "/rpi-plan payment-bug-fix"
-    description: "Plan the fix for payment issue"
-exit_criteria:
-  - "Plan document created in .claude/plans/active/"
-  - "All file modifications listed with line numbers"
-  - "Step-by-step implementation defined"
-  - "Test strategy documented"
-  - "Human approval obtained"
----
-
-# RPI Plan Phase
-
-**Purpose:** Create detailed implementation blueprint
-
-**Syntax:** `/rpi-plan [feature-name]`
-
-**Prerequisites:** Research document must exist in `.claude/research/active/`
-
----
-
-## Execution Steps
-
-### Step 1: Load Research Document
-Read `.claude/research/active/[feature]_research.md`
-
-### Step 2: Define Scope
-- In scope (explicit list)
-- Out of scope (what we're NOT touching)
-
-### Step 3: List File Modifications
-| File | Lines | Change | Risk |
-|------|-------|--------|------|
-Each modification with exact line numbers
-
-### Step 4: Create Step-by-Step Plan
-For each step:
-- Current code
-- Proposed change
-- Test to run after
-
-### Step 5: Define Test Strategy
-- Unit tests required
-- Integration tests required
-- E2E tests if applicable
-
-### Step 6: Document Rollback Plan
-- How to revert
-- Safe commit to return to
-
-### Step 7: Request Human Approval
-Plan requires human review before implementation
-
----
-
-## Output
-
-Plan document in `.claude/plans/active/[feature]_plan.md`
-
----
-
-## Context Budget
-
-- Research doc: 20k tokens
-- Plan creation: 15k tokens
-- Total: 35k tokens (17%)
-
----
-
-## Next Step
-
-After human approval: `/rpi-implement [feature-name]`
+---
+name: rpi-plan
+version: "1.0.0"
+description: "RPI Plan Phase: Create implementation blueprint with file:line precision"
+category: "rpi-orchestration"
+rpi_phase: "plan"
+context_budget_estimate: "35K tokens"
+typical_context_usage: "17%"
+prerequisites:
+  - "Research document exists in .claude/research/active/"
+  - "/rpi-research phase completed"
+outputs:
+  - "Plan document in .claude/plans/active/[name]_plan.md"
+  - "Modification table with file:line references"
+  - "Step-by-step implementation guide"
+  - "Test strategy"
+  - "Rollback plan"
+next_commands: ["/rpi-implement"]
+related_agents: ["core-architect", "database-ops", "api-developer"]
+examples:
+  - command: "/rpi-plan user-authentication"
+    description: "Create implementation plan for auth feature"
+  - command: "/rpi-plan payment-bug-fix"
+    description: "Plan the fix for payment issue"
+exit_criteria:
+  - "Plan document created in .claude/plans/active/"
+  - "All file modifications listed with line numbers"
+  - "Step-by-step implementation defined"
+  - "Test strategy documented"
+  - "Human approval obtained"
+---
+
+# RPI Plan Phase
+
+**Purpose:** Create detailed implementation blueprint
+
+**Syntax:** `/rpi-plan [feature-name]`
+
+**Prerequisites:** Research document must exist in `.claude/research/active/`
+
+---
+
+## Execution Steps
+
+### Step 1: Load Research Document
+Read `.claude/research/active/[feature]_research.md`
+
+### Step 2: Define Scope
+- In scope (explicit list)
+- Out of scope (what we're NOT touching)
+
+### Step 3: List File Modifications
+| File | Lines | Change | Risk |
+|------|-------|--------|------|
+Each modification with exact line numbers
+
+### Step 4: Create Step-by-Step Plan
+For each step:
+- Current code
+- Proposed change
+- Test to run after
+
+### Step 5: Define Test Strategy
+- Unit tests required
+- Integration tests required
+- E2E tests if applicable
+
+### Step 6: Document Rollback Plan
+- How to revert
+- Safe commit to return to
+
+### Step 7: Request Human Approval
+Plan requires human review before implementation
+
+---
+
+## Output
+
+Plan document in `.claude/plans/active/[feature]_plan.md`
+
+---
+
+## Context Budget
+
+- Research doc: 20k tokens
+- Plan creation: 15k tokens
+- Total: 35k tokens (17%)
+
+---
+
+## Next Step
+
+After human approval: `/rpi-implement [feature-name]`

package/templates/base/commands/rpi-research.md

@@ -1,88 +1,88 @@
----
-name: rpi-research
-version: "1.0.0"
-description: "RPI Research Phase: Systematic codebase exploration for feature/fix analysis"
-category: "rpi-orchestration"
-rpi_phase: "research"
-context_budget_estimate: "50K tokens"
-typical_context_usage: "25%"
-prerequisites: []
-outputs:
-  - "Research document in .claude/research/active/[name]_research.md"
-  - "File inventory with line references"
-  - "Call chain diagrams"
-  - "Dependency map"
-next_commands: ["/rpi-plan"]
-related_agents: ["context-engineer", "core-architect"]
-examples:
-  - command: "/rpi-research user-authentication"
-    description: "Research authentication flow for new feature"
-  - command: "/rpi-research payment-bug-fix"
-    description: "Investigate payment processing issue"
-exit_criteria:
-  - "Research document created in .claude/research/active/"
-  - "All relevant files identified (3-20 files)"
-  - "Call chains traced with line numbers"
-  - "Dependencies mapped"
-  - "150-word summary generated"
----
-
-# RPI Research Phase
-
-**Purpose:** Systematic, zero-code-modification exploration
-
-**Syntax:** `/rpi-research [feature-name]`
-
-**Example:**
-```bash
-/rpi-research user-authentication
-/rpi-research payment-bug-fix
-```
-
----
-
-## Execution Steps
-
-### Step 1: Initialize Research Document
-Create `.claude/research/active/[feature]_research.md` from RESEARCH_TEMPLATE.md
-
-### Step 2: Entry Point Discovery (3 parallel agents)
-- Agent 1: API/Route entry points
-- Agent 2: Business logic locations
-- Agent 3: Database/external integrations
-
-### Step 3: Call Chain Tracing
-- Read entry point files
-- Trace 3 levels deep
-- Record with file:line references
-
-### Step 4: Dependency Mapping
-- Internal service dependencies
-- External API dependencies
-
-### Step 5: Test Coverage Analysis
-- Find existing tests
-- Identify gaps
-
-### Step 6: Generate Summary
-- 150-word summary for Plan phase
-
----
-
-## Output
-
-Research document in `.claude/research/active/[feature]_research.md`
-
----
-
-## Context Budget
-
-- Target: 25% of 200k (50k tokens)
-- Compaction: After each major step
-- Final: ~20k tokens (research doc only)
-
----
-
-## Next Step
-
-After completion: `/rpi-plan [feature-name]`
+---
+name: rpi-research
+version: "1.0.0"
+description: "RPI Research Phase: Systematic codebase exploration for feature/fix analysis"
+category: "rpi-orchestration"
+rpi_phase: "research"
+context_budget_estimate: "50K tokens"
+typical_context_usage: "25%"
+prerequisites: []
+outputs:
+  - "Research document in .claude/research/active/[name]_research.md"
+  - "File inventory with line references"
+  - "Call chain diagrams"
+  - "Dependency map"
+next_commands: ["/rpi-plan"]
+related_agents: ["context-engineer", "core-architect"]
+examples:
+  - command: "/rpi-research user-authentication"
+    description: "Research authentication flow for new feature"
+  - command: "/rpi-research payment-bug-fix"
+    description: "Investigate payment processing issue"
+exit_criteria:
+  - "Research document created in .claude/research/active/"
+  - "All relevant files identified (3-20 files)"
+  - "Call chains traced with line numbers"
+  - "Dependencies mapped"
+  - "150-word summary generated"
+---
+
+# RPI Research Phase
+
+**Purpose:** Systematic, zero-code-modification exploration
+
+**Syntax:** `/rpi-research [feature-name]`
+
+**Example:**
+```bash
+/rpi-research user-authentication
+/rpi-research payment-bug-fix
+```
+
+---
+
+## Execution Steps
+
+### Step 1: Initialize Research Document
+Create `.claude/research/active/[feature]_research.md` from RESEARCH_TEMPLATE.md
+
+### Step 2: Entry Point Discovery (3 parallel agents)
+- Agent 1: API/Route entry points
+- Agent 2: Business logic locations
+- Agent 3: Database/external integrations
+
+### Step 3: Call Chain Tracing
+- Read entry point files
+- Trace 3 levels deep
+- Record with file:line references
+
+### Step 4: Dependency Mapping
+- Internal service dependencies
+- External API dependencies
+
+### Step 5: Test Coverage Analysis
+- Find existing tests
+- Identify gaps
+
+### Step 6: Generate Summary
+- 150-word summary for Plan phase
+
+---
+
+## Output
+
+Research document in `.claude/research/active/[feature]_research.md`
+
+---
+
+## Context Budget
+
+- Target: 25% of 200k (50k tokens)
+- Compaction: After each major step
+- Final: ~20k tokens (research doc only)
+
+---
+
+## Next Step
+
+After completion: `/rpi-plan [feature-name]`