ctx-cc 1.0.0 → 2.1.0

package/src/install.js

@@ -28,9 +28,9 @@ function printBanner() {
   ╚██████╗   ██║   ██╔╝ ██╗
    ╚═════╝   ╚═╝   ╚═╝  ╚═╝
 `));
-  console.log(`  ${bold('CTX')} ${dim(`v${VERSION}`)}`);
-  console.log('  Smart Context Management for Claude Code.');
-  console.log('  The GSD Killer. 12 commands, infinite power.\n');
+  console.log(`  ${bold('CTX 2.1')} ${dim(`v${VERSION}`)}`);
+  console.log('  Continuous Task eXecution for Claude Code.');
+  console.log('  8 commands. Smart routing. Debug loop.\n');
 }
 
 function copyDir(src, dest) {

package/templates/STATE.md

@@ -0,0 +1,47 @@
+# STATE.md - Living Digest
+
+> This file is the single source of truth. Updated after every action.
+> ~100 lines max. Always accurate. Always current.
+
+## Project
+- **Name**: {{project_name}}
+- **Stack**: {{tech_stack}}
+- **Status**: {{status}} <!-- initializing | planning | executing | debugging | verifying | paused -->
+
+## Current Phase
+- **ID**: {{phase_id}}
+- **Goal**: {{phase_goal}}
+- **Progress**: {{completed_tasks}}/{{total_tasks}} tasks
+
+## Active Task
+- **Task**: {{current_task}}
+- **Status**: {{task_status}} <!-- pending | in_progress | blocked | debugging | done -->
+- **Attempts**: {{attempt_count}}/5
+
+## Debug Session (if active)
+- **Issue**: {{debug_issue}}
+- **Hypothesis**: {{current_hypothesis}}
+- **Attempt**: {{debug_attempt}}/5
+- **Last Error**: {{last_error}}
+- **Browser Verified**: {{browser_verified}} <!-- false | true -->
+
+## Context Budget
+- **Used**: {{context_percent}}%
+- **Quality**: {{quality_level}} <!-- peak | good | degrading | poor -->
+- **Action**: {{recommended_action}} <!-- continue | checkpoint-soon | checkpoint-now -->
+
+## Recent Decisions
+<!-- Last 5 decisions, newest first -->
+1. {{decision_1}}
+2. {{decision_2}}
+3. {{decision_3}}
+
+## Blockers
+<!-- Current blockers requiring user input -->
+- {{blocker_1}}
+
+## Next Action
+> {{next_action_description}}
+
+---
+*Last updated: {{timestamp}}*

package/commands/do.md

@@ -1,130 +0,0 @@
----
-name: ctx:do
-description: Execute current phase or run a quick task
-args: "[task]"
----
-
-<objective>
-Execute the current phase's plan, OR run a quick task if an argument is provided.
-</objective>
-
-<process>
-
-<step name="check_mode">
-If argument provided (e.g., `/ctx:do "fix the login bug"`):
-  → Quick Task Mode
-
-If no argument:
-  → Phase Execution Mode
-</step>
-
-<!-- QUICK TASK MODE -->
-<step name="quick_task" condition="argument provided">
-Quick task mode - bypass full workflow:
-
-1. Read the task description
-2. Load relevant context from memory
-3. Execute the task directly
-4. Create atomic git commit
-5. Update memory with what was done
-
-```
-## Quick Task
-
-**Task:** {task description}
-**Status:** In Progress
-
-Executing without full planning workflow...
-```
-
-Skip to `complete_task` step.
-</step>
-
-<!-- PHASE EXECUTION MODE -->
-<step name="load_phase">
-Load current phase from `.ctx/ROADMAP.md`:
-
-1. Find phase with status "in_progress" or first "pending"
-2. Load `.ctx/phases/{phase-id}/PLAN.md`
-3. Load `.ctx/phases/{phase-id}/PROGRESS.md`
-
-If no phase found:
-```
-No phase to execute. Run `/ctx:plan <goal>` first.
-```
-</step>
-
-<step name="load_context">
-JIT context loading:
-
-1. Load relevant facts from memory
-2. Load file index for files mentioned in plan
-3. Retrieve only needed files (not entire codebase)
-
-Target: Minimal context for current task.
-</step>
-
-<step name="execute_tasks">
-For each task in PLAN.md:
-
-1. **Start task**
-   - Update PROGRESS.md: task status → "in_progress"
-   - Load task-specific files
-
-2. **Execute**
-   - Implement the task
-   - Follow deviation rules:
-     - Bug in existing code → Auto-fix, document
-     - Missing validation → Auto-add, document
-     - Blocking issue → Auto-fix, document
-     - Architectural decision → STOP, ask user
-
-3. **Commit**
-   - Atomic git commit for the task
-   - Message: "ctx: {task title}"
-
-4. **Update progress**
-   - Mark task complete in PROGRESS.md
-   - Extract facts to memory
-   - Check context budget
-
-5. **Context check**
-   - If context > 50%: trigger auto-checkpoint
-   - Signal user if split recommended
-</step>
-
-<step name="complete_task">
-After task/phase completion:
-
-```
-## Task Complete
-
-**Task:** {description}
-**Files changed:** {list}
-**Commit:** {hash}
-
-**Context:** {percentage}%
-{If > 50%: "Consider `/ctx:pause` to checkpoint."}
-
-**Next:** {next task or "Run `/ctx:verify` to validate"}
-```
-</step>
-
-</process>
-
-<deviation_rules>
-| Rule | Trigger | Action |
-|------|---------|--------|
-| 1 | Bug in existing code | Auto-fix, document in commit |
-| 2 | Missing validation | Auto-add, document |
-| 3 | Blocking issue | Auto-fix, document |
-| 4 | Architectural decision | **STOP** - ask user |
-</deviation_rules>
-
-<success_criteria>
-- [ ] Task executed successfully
-- [ ] Atomic git commit created
-- [ ] PROGRESS.md updated
-- [ ] Memory updated with facts
-- [ ] Context budget monitored
-</success_criteria>

package/commands/forget.md

@@ -1,58 +0,0 @@
----
-name: ctx:forget
-description: Remove a fact from memory
-args: "<id>"
----
-
-<objective>
-Remove a specific fact from CTX memory by its ID.
-</objective>
-
-<process>
-
-<step name="find_fact">
-Search all memory tiers for the fact ID.
-
-If not found:
-```
-Fact "{id}" not found in memory.
-Use `/ctx:recall {query}` to find fact IDs.
-```
-</step>
-
-<step name="confirm">
-Show the fact before removal:
-
-```
-## Forget Fact
-
-**ID:** {id}
-**Content:** {fact}
-**Category:** {category}
-**Stored:** {timestamp}
-
-Are you sure you want to remove this fact?
-This cannot be undone.
-```
-</step>
-
-<step name="remove">
-Delete the fact from its memory tier.
-
-```
-## Fact Forgotten
-
-**ID:** {id}
-**Content:** {fact}
-
-Removed from {tier} memory.
-```
-</step>
-
-</process>
-
-<success_criteria>
-- [ ] Fact located by ID
-- [ ] Confirmation shown
-- [ ] Fact removed from correct tier
-</success_criteria>

package/commands/phase-add.md

@@ -1,53 +0,0 @@
----
-name: ctx:phase-add
-description: Add a new phase to the roadmap
-args: "<name>"
----
-
-<objective>
-Add a new phase to the project roadmap.
-</objective>
-
-<process>
-
-<step name="validate">
-Check `.ctx/ROADMAP.md` exists. If not:
-```
-CTX not initialized. Run `/ctx:init` first.
-```
-</step>
-
-<step name="get_details">
-Ask user for phase details:
-
-1. **Goal**: What should this phase achieve?
-2. **Priority**: Where in the roadmap? (next, end, after phase X)
-</step>
-
-<step name="create_phase">
-1. Generate phase ID from name (slugified)
-2. Create phase directory: `.ctx/phases/{phase-id}/`
-3. Add to ROADMAP.md in specified position
-4. Set status to "pending"
-</step>
-
-<step name="output">
-```
-## Phase Added
-
-**Name:** {name}
-**ID:** {phase-id}
-**Position:** #{position} in roadmap
-**Status:** pending
-
-**Next:** Run `/ctx:plan {name}` to create the plan.
-```
-</step>
-
-</process>
-
-<success_criteria>
-- [ ] Phase added to ROADMAP.md
-- [ ] Phase directory created
-- [ ] Position correct in roadmap
-</success_criteria>

package/commands/phase-list.md

@@ -1,46 +0,0 @@
----
-name: ctx:phase-list
-description: Show all phases with status
----
-
-<objective>
-Display all phases in the roadmap with their current status.
-</objective>
-
-<process>
-
-<step name="load_roadmap">
-Read `.ctx/ROADMAP.md` and parse phases.
-
-If not found:
-```
-CTX not initialized. Run `/ctx:init` first.
-```
-</step>
-
-<step name="display_phases">
-```
-## Project Phases
-
-| # | Phase | Status | Progress | Verified |
-|---|-------|--------|----------|----------|
-| 1 | {name} | complete | 100% | ✓ |
-| 2 | {name} | in_progress | 60% | - |
-| 3 | {name} | pending | 0% | - |
-
-**Current:** Phase 2 - {name}
-**Remaining:** {count} phases
-
-**Next action:**
-  - If current incomplete: `/ctx:do`
-  - If current done: `/ctx:verify` then `/ctx:phase next`
-```
-</step>
-
-</process>
-
-<success_criteria>
-- [ ] All phases listed with accurate status
-- [ ] Current phase highlighted
-- [ ] Next action suggested
-</success_criteria>

package/commands/phase-next.md

@@ -1,67 +0,0 @@
----
-name: ctx:phase-next
-description: Move to the next phase in the roadmap
----
-
-<objective>
-Complete current phase and move to the next one.
-</objective>
-
-<process>
-
-<step name="check_current">
-Load current phase from `.ctx/ROADMAP.md`.
-
-If current phase not verified:
-```
-⚠ Current phase not verified.
-   Run `/ctx:verify` first to ensure phase is complete.
-```
-</step>
-
-<step name="complete_current">
-1. Mark current phase as "complete" in ROADMAP.md
-2. Update completion timestamp
-3. Archive phase state to memory
-</step>
-
-<step name="activate_next">
-1. Find next "pending" phase
-2. Mark it as "in_progress"
-3. Load phase details
-
-If no next phase:
-```
-## All Phases Complete!
-
-No more phases in the roadmap.
-
-**Options:**
-  - `/ctx:ship` - Run final audit
-  - `/ctx:phase add <name>` - Add more phases
-```
-</step>
-
-<step name="output">
-```
-## Phase Transition
-
-**Completed:** {previous phase}
-**Now Active:** {next phase}
-
-**Phase Goal:** {goal}
-**Tasks:** {count from PLAN.md or "Not planned yet"}
-
-**Next:**
-  - If not planned: `/ctx:plan {goal}`
-  - If planned: `/ctx:do`
-```
-</step>
-
-</process>
-
-<success_criteria>
-- [ ] Previous phase marked complete
-- [ ] Next phase activated
-- [ ] Clear guidance on next steps
-</success_criteria>

package/commands/recall.md

@@ -1,72 +0,0 @@
----
-name: ctx:recall
-description: Query memory for relevant facts
-args: "<query>"
----
-
-<objective>
-Search CTX memory for facts matching the query. Returns relevant information from all memory tiers.
-</objective>
-
-<process>
-
-<step name="search_memory">
-Search across all memory tiers:
-
-1. **Working memory** - Current session facts
-2. **Episodic memory** - Cross-session facts
-3. **Semantic memory** - Permanent knowledge
-
-Match by:
-- Keyword matching
-- Category filtering
-- Relevance scoring
-</step>
-
-<step name="rank_results">
-Rank results by:
-1. Recency (newer facts first)
-2. Relevance to query
-3. Importance (manual > auto-extracted)
-</step>
-
-<step name="display">
-```
-## Memory Recall: "{query}"
-
-### Results ({count} found)
-
-**From Episodic Memory:**
-1. [{id}] {fact} ({timestamp})
-2. [{id}] {fact} ({timestamp})
-
-**From Semantic Memory:**
-3. [{id}] {fact} (permanent)
-
-**From Working Memory:**
-4. [{id}] {fact} (current session)
-
----
-To forget a fact: `/ctx:forget {id}`
-```
-
-If no results:
-```
-## Memory Recall: "{query}"
-
-No matching facts found.
-
-**Tips:**
-- Try broader keywords
-- Check `/ctx:status` for memory stats
-- Use `/ctx:remember` to add facts
-```
-</step>
-
-</process>
-
-<success_criteria>
-- [ ] All memory tiers searched
-- [ ] Results ranked by relevance
-- [ ] IDs provided for management
-</success_criteria>

package/commands/remember.md

@@ -1,68 +0,0 @@
----
-name: ctx:remember
-description: Force-remember an important fact
-args: "<fact>"
----
-
-<objective>
-Manually add a fact to CTX memory. Use for important information that should persist across sessions.
-</objective>
-
-<process>
-
-<step name="validate">
-Check `.ctx/memory/` exists. Create if not.
-</step>
-
-<step name="categorize">
-Determine fact category:
-- **decision**: Architectural or design decisions
-- **pattern**: Code patterns to follow
-- **constraint**: Limitations or requirements
-- **context**: Project-specific context
-- **preference**: User preferences
-</step>
-
-<step name="store">
-Add to appropriate memory tier:
-
-1. **Working memory** (current session): `.ctx/memory/working/`
-2. **Episodic memory** (cross-session): `.ctx/memory/episodic/`
-3. **Semantic memory** (permanent): `.ctx/memory/semantic/`
-
-For manual `/ctx:remember`, store in **episodic** by default.
-
-Format:
-```json
-{
-  "id": "{uuid}",
-  "content": "{fact}",
-  "category": "{category}",
-  "timestamp": "{iso-8601}",
-  "source": "manual"
-}
-```
-</step>
-
-<step name="confirm">
-```
-## Fact Remembered
-
-**ID:** {short-id}
-**Category:** {category}
-**Content:** {fact}
-**Stored in:** Episodic memory
-
-This fact will be available in future sessions.
-To query: `/ctx:recall {keywords}`
-To remove: `/ctx:forget {id}`
-```
-</step>
-
-</process>
-
-<success_criteria>
-- [ ] Fact stored in memory
-- [ ] ID assigned for retrieval
-- [ ] Category determined
-</success_criteria>

package/commands/resume.md

@@ -1,108 +0,0 @@
----
-name: ctx:resume
-description: Resume from last checkpoint
-args: "[checkpoint-id]"
----
-
-<objective>
-Resume work from a checkpoint. Restores context efficiently (~2-3k tokens instead of full reload).
-</objective>
-
-<process>
-
-<step name="find_checkpoint">
-If checkpoint-id provided:
-  Load `.ctx/checkpoints/{checkpoint-id}/`
-
-If no checkpoint-id:
-  Load most recent checkpoint from `.ctx/checkpoints/`
-
-If no checkpoints exist:
-```
-No checkpoints found.
-
-**Options:**
-- Start fresh with `/ctx:init`
-- Check `.ctx/` exists
-```
-</step>
-
-<step name="load_state">
-Load checkpoint state:
-
-1. **HANDOFF.md** - Read for context
-2. **state.json** - Parse current state
-3. **working-memory.json** - Load recent facts
-4. **file-index.json** - Know relevant files
-</step>
-
-<step name="restore_context">
-Build minimal context:
-
-1. Load semantic memory (permanent facts)
-2. Load recent episodic memory (relevant to phase)
-3. Load working memory from checkpoint
-4. Identify files to read (from file-index)
-
-Target: ~2-3k tokens for full context restoration.
-</step>
-
-<step name="verify_sync">
-Check for changes since checkpoint:
-
-```bash
-git status
-git log --oneline {checkpoint-commit}..HEAD
-```
-
-If changes found:
-```
-⚠ Changes detected since checkpoint:
-  - {files changed}
-
-These will be incorporated into current state.
-```
-</step>
-
-<step name="output">
-```
-## Session Resumed
-
-**Checkpoint:** {id}
-**Created:** {timestamp}
-**Phase:** {phase name}
-**Progress:** {percentage}%
-
-**Context Restored:** ~{token count} tokens
-
-**Where We Left Off:**
-{handoff summary}
-
-**Next Task:**
-{next task from plan}
-
-**Ready to continue.** Run `/ctx:do` to proceed.
-```
-</step>
-
-</process>
-
-<context_budget>
-| Component | Tokens |
-|-----------|--------|
-| Semantic facts | ~1,000 |
-| Recent decisions | ~500 |
-| Patterns | ~300 |
-| Task state | ~200 |
-| File identifiers | ~500 |
-| **Total** | **~2,500** |
-
-vs. Naive reload: 50,000+ tokens
-</context_budget>
-
-<success_criteria>
-- [ ] Checkpoint loaded correctly
-- [ ] Context restored efficiently
-- [ ] Sync with git verified
-- [ ] Clear next steps provided
-</success_criteria>