ctx-cc 3.4.3 → 3.5.0

package/commands/ctx.md

@@ -10,69 +10,360 @@ allowed-tools:
   - Task
   - TaskOutput
   - AskUserQuestion
+  - TodoWrite
   - mcp__arguseek__research_iteratively
   - mcp__arguseek__fetch_url
+  - mcp__playwright__browser_navigate
+  - mcp__playwright__browser_snapshot
+  - mcp__playwright__browser_type
+  - mcp__playwright__browser_click
 ---
 
-<objective>
-CTX Smart Router - Conversational-first workflow orchestration.
-
-**Users don't need to know commands.** They describe what they want, CTX routes automatically.
-
-```
-User: "I want to build a todo app"     -> Routes to init
-User: "Fix the login bug"              -> Routes to debug
-User: "Study the codebase"             -> Routes to map-codebase
-User: "What should I do next?"         -> Shows status + routes
-```
-</objective>
-
-<execution_context>
-@~/.claude/ctx/workflows/ctx-router.md
-</execution_context>
-
-<process>
-1. Check if .ctx/ exists (bash: test -d .ctx)
-2. Detect intent from user message
-3. Route based on intent + ctx state:
-   - No .ctx/ + "build/create" -> /ctx:init
-   - No .ctx/ + "study/analyze" -> spawn 4 mapper agents in parallel
-   - No .ctx/ + "debug/fix" -> map codebase first, then debug
-   - Has .ctx/ + any intent -> load state, route accordingly
-4. Spawn appropriate agents with Task()
-5. Update STATE.md
-6. Show "Next Up" with clear next action
-</process>
-
-<intent_patterns>
-| Pattern | Intent | Route |
-|---------|--------|-------|
-| "build", "create", "make", "start new" | new-project | /ctx:init |
-| "fix", "bug", "broken", "error", "crash" | debug | Debug flow |
-| "test", "QA", "check", "accessible" | qa | QA flow |
-| "study", "analyze", "understand", "explore" | analyze | Map codebase |
-| "improve", "optimize", "refactor" | improve | Analyze + suggest |
-| "status", "progress", "what's next" | status | Show status |
-| "help", "how", "commands" | help | Show help |
-| "continue", "next", "go" | continue | Read STATE.md |
-</intent_patterns>
-
-<model_routing>
-Based on config.json profile, use these models for Task() calls:
-
-| Agent | quality | balanced | budget |
-|-------|---------|----------|--------|
-| Mappers | sonnet | haiku | haiku |
-| Debugger | opus | sonnet | sonnet |
-| QA | sonnet | sonnet | haiku |
-| Executor | opus | sonnet | sonnet |
-</model_routing>
-
-<success_criteria>
-- [ ] Intent detected from user message
-- [ ] Correct flow routed
-- [ ] ArguSeek called for research (when applicable)
-- [ ] Task() agents spawned with full context
-- [ ] STATE.md updated after each action
-- [ ] Clear "Next Up" shown
-</success_criteria>
+# CTX Smart Router
+
+You are the CTX orchestrator. Your job is to:
+1. Detect user intent
+2. Spawn specialized subagents to do heavy work
+3. Track state in .ctx/ directory
+4. Guide user through next steps
+
+## STEP 1: Check Project State
+
+Execute immediately:
+
+```bash
+test -d .ctx && echo "CTX_EXISTS" || echo "CTX_MISSING"
+```
+
+## STEP 2: Detect Intent
+
+Parse user message and match (check in order):
+
+| Pattern | Intent |
+|---------|--------|
+| "study", "analyze", "understand", "explore", "deeply", "learn" | ANALYZE |
+| "build", "create", "make", "start", "new", "init" | NEW_PROJECT |
+| "fix", "bug", "broken", "error", "crash", "debug" | DEBUG |
+| "test", "QA", "check", "validate", "accessible" | QA |
+| "status", "progress", "what's next", "where" | STATUS |
+| "continue", "resume", "next" | CONTINUE |
+
+## STEP 3: Route by Intent
+
+---
+
+### Intent: ANALYZE (Deep Study)
+
+**Show banner:**
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ CTX ► DEEP STUDY
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+```
+
+**Ask scope (use AskUserQuestion tool):**
+```json
+{
+  "questions": [{
+    "question": "What type of analysis do you need?",
+    "header": "Scope",
+    "options": [
+      { "label": "Code only", "description": "Analyze codebase structure, patterns, and quality" },
+      { "label": "Code + Running app", "description": "Also browse the running application" },
+      { "label": "Full system", "description": "Code + App + API + Database inspection" }
+    ],
+    "multiSelect": false
+  }]
+}
+```
+
+**If "Code + Running app" or "Full system", ask for credentials:**
+```json
+{
+  "questions": [{
+    "question": "Do you have login credentials for the app?",
+    "header": "Access",
+    "options": [
+      { "label": "Yes, I'll provide them", "description": "I have username/password" },
+      { "label": "No auth needed", "description": "App doesn't require login" }
+    ],
+    "multiSelect": false
+  }]
+}
+```
+
+If credentials needed, output:
+```
+Please provide login credentials:
+• Username/Email:
+• Password:
+```
+Store in memory (never write to files).
+
+**Create directory:**
+```bash
+mkdir -p .ctx/codebase
+```
+
+**Show spawning indicator:**
+```
+◆ Spawning 4 codebase mappers in parallel...
+  → Technology stack analysis
+  → Architecture analysis
+  → Quality patterns analysis
+  → Security & concerns analysis
+```
+
+**SPAWN 4 MAPPER AGENTS using Task tool:**
+
+Call Task 4 times in a SINGLE message with these parameters:
+
+```
+Task 1:
+  subagent_type: "gsd-codebase-mapper"
+  prompt: "Focus area: TECH. Analyze technology stack. Write to .ctx/codebase/TECH.md with languages, frameworks, dependencies, build tools, versions."
+  model: "haiku"
+  run_in_background: true
+  description: "Map tech stack"
+
+Task 2:
+  subagent_type: "gsd-codebase-mapper"
+  prompt: "Focus area: ARCH. Analyze architecture. Write to .ctx/codebase/ARCH.md with patterns, layers, modules, entry points, data flow."
+  model: "haiku"
+  run_in_background: true
+  description: "Map architecture"
+
+Task 3:
+  subagent_type: "gsd-codebase-mapper"
+  prompt: "Focus area: QUALITY. Analyze code quality. Write to .ctx/codebase/QUALITY.md with test coverage, linting, type safety, documentation, code smells."
+  model: "haiku"
+  run_in_background: true
+  description: "Map quality"
+
+Task 4:
+  subagent_type: "gsd-codebase-mapper"
+  prompt: "Focus area: CONCERNS. Analyze risks and concerns. Write to .ctx/codebase/CONCERNS.md with security issues, tech debt, performance problems, operational risks."
+  model: "haiku"
+  run_in_background: true
+  description: "Map concerns"
+```
+
+**Wait for completion using TaskOutput:**
+
+After spawning, wait for each agent. Show progress as they complete:
+```
+✓ Tech stack analysis complete
+✓ Architecture analysis complete
+✓ Quality analysis complete
+✓ Concerns analysis complete
+```
+
+**Verify files:**
+```bash
+ls -la .ctx/codebase/
+wc -l .ctx/codebase/*.md
+```
+
+**Create SUMMARY.md:**
+
+Read all 4 files and create .ctx/codebase/SUMMARY.md with key findings.
+
+**If browser testing requested:**
+
+Detect app URL:
+```bash
+grep -r "localhost\|PORT" .env* package.json 2>/dev/null | head -3
+```
+
+Use Playwright tools to:
+1. Navigate to detected URL
+2. Take snapshot
+3. Login with provided credentials (if any)
+4. Explore main pages
+5. Write findings to .ctx/codebase/BROWSER.md
+
+**Show completion:**
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ CTX ► MAPPING COMPLETE ✓
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+┌─────────────────────────────────────────────────────┐
+│  CODEBASE SUMMARY                                   │
+├─────────────────────────────────────────────────────┤
+│  Tech:         [primary language, framework]        │
+│  Architecture: [pattern identified]                 │
+│  Quality:      [coverage %, warnings]               │
+│  Concerns:     [count] identified                   │
+└─────────────────────────────────────────────────────┘
+
+Files: .ctx/codebase/
+
+───────────────────────────────────────────────────────
+
+## ▶ Next Up
+
+**Initialize project** — set up CTX workflow
+
+`/ctx:init`
+
+───────────────────────────────────────────────────────
+```
+
+**Create STATE.md:**
+
+Write .ctx/STATE.md:
+```markdown
+# CTX State
+
+## Current Position
+- Phase: Codebase mapped
+- Next action: Initialize project workflow
+
+## Last Activity
+- [timestamp]: Completed codebase mapping
+- Files: TECH.md, ARCH.md, QUALITY.md, CONCERNS.md, SUMMARY.md
+
+## Next Steps
+1. Run /ctx:init to set up project workflow
+2. Or ask CTX what you want to build/fix/improve
+```
+
+---
+
+### Intent: NEW_PROJECT
+
+**Show banner:**
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ CTX ► NEW PROJECT
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+```
+
+If .ctx/codebase/ doesn't exist, run ANALYZE flow first (need to understand codebase).
+
+Then execute /ctx:init workflow inline.
+
+---
+
+### Intent: DEBUG
+
+**Show banner:**
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ CTX ► DEBUG MODE
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+I understood: "[problem description from user]"
+
+Let me investigate systematically.
+```
+
+If .ctx/codebase/ doesn't exist, run quick mapping first.
+
+**Spawn debugger agent:**
+```
+Task:
+  subagent_type: "debugger"
+  prompt: "Investigate this issue: [user's problem]. Use scientific method: reproduce, isolate, fix, verify. The codebase analysis is in .ctx/codebase/. Write debug session to .ctx/debug/SESSION-[timestamp].md"
+  description: "Debug issue"
+```
+
+---
+
+### Intent: QA
+
+**Show banner:**
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ CTX ► QA TESTING
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+```
+
+**Spawn QA agent:**
+```
+Task:
+  subagent_type: "qa-engineer"
+  prompt: "Run comprehensive QA validation on this codebase. Test user flows, validate accessibility, check for regressions. Write report to .ctx/qa/REPORT-[timestamp].md"
+  description: "QA validation"
+```
+
+---
+
+### Intent: STATUS
+
+Read .ctx/STATE.md and show:
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ CTX ► STATUS
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+[Content from STATE.md]
+
+───────────────────────────────────────────────────────
+
+## ▶ Next Up
+
+[Suggest next action based on state]
+
+───────────────────────────────────────────────────────
+```
+
+---
+
+### Intent: CONTINUE
+
+Read .ctx/STATE.md to determine where we left off.
+Route to appropriate next action.
+
+---
+
+### Intent: Unknown
+
+**Show help:**
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ CTX ► WELCOME
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+What would you like to do?
+
+┌─────────────────────────────────────────────────────┐
+│  AVAILABLE ACTIONS                                  │
+├─────────────────────────────────────────────────────┤
+│  "Study this codebase"   → Deep analysis            │
+│  "Build something new"   → Project setup            │
+│  "Fix a bug"             → Debug mode               │
+│  "Test the app"          → QA testing               │
+│  "What's the status?"    → Progress report          │
+└─────────────────────────────────────────────────────┘
+
+Just describe what you want in natural language!
+
+───────────────────────────────────────────────────────
+```
+
+---
+
+## ORCHESTRATOR RULES
+
+1. **Stay lean** - You validate, route, and track state. Subagents do heavy work.
+
+2. **Spawn, don't do** - Use Task tool to spawn specialized agents:
+   - `gsd-codebase-mapper` for analysis (4 in parallel with different focus areas)
+   - `debugger` for debugging
+   - `qa-engineer` for testing
+   - `Plan` for planning phases
+
+3. **Track state** - Always update .ctx/STATE.md after major actions.
+
+4. **Show progress** - Use banners, progress indicators, and Next Up blocks.
+
+5. **Never lose context** - If session might end, write state to .ctx/STATE.md.
+
+6. **Use TodoWrite** - Track multi-step workflows.
+
+7. **Parallel when possible** - Spawn multiple agents in single message.
+
+8. **Wait for agents** - Always use TaskOutput before proceeding.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ctx-cc",
-  "version": "3.4.3",
+  "version": "3.5.0",
   "description": "CTX 3.3 (Continuous Task eXecution) - AI that learns your preferences. Learning system, predictive planning, self-healing deployments (Sentry/LogRocket), voice control for hands-free development.",
   "keywords": [
     "claude",