@cluesmith/codev 2.0.0-rc.6 → 2.0.0-rc.61

package/skeleton/protocols/tick/protocol.md

@@ -3,16 +3,16 @@
 
 ## Overview
 
-TICK is an **amendment workflow** for existing SPIDER specifications. Rather than creating new standalone specs, TICK modifies existing spec and plan documents in-place, tracking changes in an "Amendments" section.
+TICK is an **amendment workflow** for existing SPIR specifications. Rather than creating new standalone specs, TICK modifies existing spec and plan documents in-place, tracking changes in an "Amendments" section.
 
-**Core Principle**: TICK is for *refining* existing specs. SPIDER is for *creating* new specs.
+**Core Principle**: TICK is for *refining* existing specs. SPIR is for *creating* new specs.
 
-**Key Insight**: TICKs are not small SPIDERs - they're amendments to existing SPIDERs. This eliminates the "TICK vs SPIDER" decision problem and keeps related work together.
+**Key Insight**: TICKs are not small SPIRs - they're amendments to existing SPIRs. This eliminates the "TICK vs SPIR" decision problem and keeps related work together.
 
 ## When to Use TICK
 
 ### Use TICK when:
-- Making **amendments to an existing SPIDER spec** that is already `integrated`
+- Making **amendments to an existing SPIR spec** that is already `integrated`
 - Small scope (< 300 lines of new/changed code)
 - Requirements are clear and well-defined
 - No fundamental architecture changes
@@ -23,7 +23,7 @@ TICK is an **amendment workflow** for existing SPIDER specifications. Rather tha
   - Utility function additions to existing modules
   - Refactoring within an existing feature
 
-### Use SPIDER instead when:
+### Use SPIR instead when:
 - Creating a **new feature from scratch** (no existing spec to amend)
 - Major architecture changes (scope too large for amendment)
 - Unclear requirements needing exploration
@@ -31,8 +31,8 @@ TICK is an **amendment workflow** for existing SPIDER specifications. Rather tha
 - Multiple stakeholders need alignment
 
 ### Cannot Use TICK when:
-- No relevant SPIDER spec exists (create a new SPIDER spec instead)
-- Target spec is not yet `integrated` (complete the SPIDER cycle first)
+- No relevant SPIR spec exists (create a new SPIR spec instead)
+- Target spec is not yet `integrated` (complete the SPIR cycle first)
 
 ## Amendment Workflow
 
@@ -162,9 +162,9 @@ The format `[TICK ####-NNN]` identifies:
 - `####`: Parent spec number (e.g., 0002)
 - `NNN`: TICK amendment number (e.g., 001, 002, 003)
 
-## Key Differences from SPIDER
+## Key Differences from SPIR
 
-| Aspect | SPIDER | TICK |
+| Aspect | SPIR | TICK |
 |--------|--------|------|
 | Purpose | Create new features | Amend existing features |
 | File creation | Creates new spec/plan/review | Modifies spec/plan, creates review |
@@ -178,16 +178,16 @@ The format `[TICK ####-NNN]` identifies:
 
 ```
 Is there an existing spec to amend?
-├── NO → Use SPIDER (create new spec)
+├── NO → Use SPIR (create new spec)
 └── YES → Is it integrated?
-    ├── NO → Complete SPIDER cycle first
+    ├── NO → Complete SPIR cycle first
     └── YES → Is the change small (<300 LOC)?
         ├── YES → Use TICK (amend existing spec)
-        └── NO → Use SPIDER (scope too large)
+        └── NO → Use SPIR (scope too large)
 ```
 
 **Mental Model**:
-- SPIDER = Create new feature from scratch
+- SPIR = Create new feature from scratch
 - TICK = Refine/extend existing feature
 
 ## Example TICK Workflow
@@ -251,7 +251,7 @@ Existing standalone TICK projects (created before this protocol change) are gran
 1. **Single source of truth**: Spec file shows complete feature evolution
 2. **Clear history**: Amendments section documents all changes chronologically
 3. **Reduced fragmentation**: Related work stays together
-4. **Simpler mental model**: "New vs amendment" is clearer than "SPIDER vs TICK"
+4. **Simpler mental model**: "New vs amendment" is clearer than "SPIR vs TICK"
 5. **Preserved context**: Looking at a spec shows all refinements
 
 ## Limitations
@@ -264,14 +264,14 @@ Existing standalone TICK projects (created before this protocol change) are gran
 ## Best Practices
 
 1. **Verify spec is integrated**: Never TICK a spec that isn't complete
-2. **Keep TICKs small**: If scope grows, consider new SPIDER spec
+2. **Keep TICKs small**: If scope grows, consider new SPIR spec
 3. **Clear summaries**: Amendment entries should be self-explanatory
 4. **Test before review**: Always test functionality before presenting
 5. **Honest documentation**: Document all deviations in review
 
 ## Templates
 
-TICK uses the standard SPIDER templates with amendments sections:
-- Spec template: `codev/protocols/spider/templates/spec.md` (includes Amendments section)
-- Plan template: `codev/protocols/spider/templates/plan.md` (includes Amendment History section)
+TICK uses the standard SPIR templates with amendments sections:
+- Spec template: `codev/protocols/spir/templates/spec.md` (includes Amendments section)
+- Plan template: `codev/protocols/spir/templates/plan.md` (includes Amendment History section)
 - Review template: `codev/protocols/tick/templates/review.md` (TICK-specific)

package/skeleton/protocols/tick/templates/review.md

@@ -77,7 +77,7 @@
 
 ## TICK Protocol Feedback
 - **Autonomous execution**: [Worked well / Issues encountered]
-- **Single-phase approach**: [Appropriate / Should have used SPIDER]
+- **Single-phase approach**: [Appropriate / Should have used SPIR]
 - **Speed vs quality trade-off**: [Balanced / Too fast / Too slow]
 - **End-only consultation**: [Caught issues / Missed opportunities]
 

package/skeleton/resources/commands/agent-farm.md

@@ -18,12 +18,16 @@ af <command> [options]
 
 ## Commands
 
-### af start
+### af dash
+
+Project dashboard commands - start/stop the architect dashboard for this project.
+
+#### af dash start
 
 Start the architect dashboard.
 
 ```bash
-af start [options]
+af dash start [options]
 ```
 
 **Options:**
@@ -47,16 +51,16 @@ The dashboard is accessible via browser at `http://localhost:<port>`.
 
 ```bash
 # Start with defaults
-af start
+af dash start
 
 # Start with custom port
-af start -p 4300
+af dash start -p 4300
 
 # Start with specific command
-af start -c "claude --model opus"
+af dash start -c "claude --model opus"
 
 # Start on remote machine
-af start --remote user@host
+af dash start --remote user@host
 ```
 
 #### Remote Access
@@ -65,13 +69,13 @@ Start Agent Farm on a remote machine and access it from your local workstation w
 
 ```bash
 # On your local machine - one command does everything:
-af start --remote user@remote-host
+af dash start --remote user@remote-host
 
 # Or with explicit project path:
-af start --remote user@remote-host:/path/to/project
+af dash start --remote user@remote-host:/path/to/project
 
 # With custom port:
-af start --remote user@remote-host --port 4300
+af dash start --remote user@remote-host --port 4300
 ```
 
 This single command:
@@ -112,19 +116,17 @@ export PATH="$HOME/.local/bin:$PATH"
 
 ```bash
 # DEPRECATED: Exposes dashboard without authentication
-af start --allow-insecure-remote
+af dash start --allow-insecure-remote
 ```
 
 The `--allow-insecure-remote` flag binds to `0.0.0.0` with no authentication. Use `--remote` instead for secure access via SSH.
 
----
+#### af dash stop
 
-### af stop
-
-Stop all agent farm processes.
+Stop all agent farm processes for this project.
 
 ```bash
-af stop
+af dash stop
 ```
 
 **Description:**
@@ -306,16 +308,14 @@ af open src/auth/login.ts
 
 ---
 
-### af util
+### af shell
 
 Spawn a utility shell terminal.
 
 ```bash
-af util [options]
+af shell [options]
 ```
 
-**Aliases:** `af shell`
-
 **Options:**
 - `-n, --name <name>` - Name for the shell terminal
 
@@ -330,10 +330,10 @@ Opens a general-purpose shell terminal in the dashboard. Useful for:
 
 ```bash
 # Open utility shell
-af util
+af shell
 
 # Open with custom name
-af util -n "test-runner"
+af shell -n "test-runner"
 ```
 
 ---
@@ -358,25 +358,6 @@ af rename 0042 "auth-rework"
 
 ---
 
-### af tutorial
-
-Interactive tutorial for new users.
-
-```bash
-af tutorial [options]
-```
-
-**Options:**
-- `--reset` - Start tutorial fresh
-- `--skip` - Skip current step
-- `--status` - Show tutorial progress
-
-**Description:**
-
-Walks through the basics of using agent-farm with guided steps.
-
----
-
 ### af ports
 
 Manage global port registry.
@@ -410,7 +391,7 @@ Removes entries for projects that no longer exist.
 
 ### af tower
 
-Manage the tower dashboard.
+Manage the cross-project tower dashboard. Tower shows all agent-farm instances across projects.
 
 #### af tower start
 
@@ -422,6 +403,7 @@ af tower start [options]
 
 **Options:**
 - `-p, --port <port>` - Port to run on (default: 4100)
+- `-w, --web` - Enable web access mode (requires CODEV_WEB_KEY)
 
 #### af tower stop
 
@@ -495,7 +477,7 @@ af db stats [options]
 
 ## Configuration
 
-Customize commands via `codev/config.json`:
+Customize commands via `af-config.json` at the project root:
 
 ```json
 {
@@ -522,7 +504,7 @@ af spawn -p 0042 --builder-cmd "claude --model haiku"
 |------|-------------|
 | `.agent-farm/state.json` | Project runtime state |
 | `~/.agent-farm/ports.json` | Global port registry |
-| `codev/config.json` | Project configuration |
+| `af-config.json` | Agent Farm configuration (project root) |
 
 ---
 

package/skeleton/resources/commands/overview.md

@@ -21,7 +21,7 @@ codev adopt
 codev doctor
 
 # Start the architect dashboard
-af start
+af dash start
 
 # Consult an AI model about a spec
 consult -m gemini spec 42
@@ -46,7 +46,6 @@ This installs all three commands globally: `codev`, `af`, and `consult`.
 | `codev doctor` | Check system dependencies |
 | `codev update` | Update codev templates and protocols |
 | `codev import <source>` | AI-assisted protocol import from other projects |
-| `codev tower` | Cross-project dashboard |
 
 See [codev.md](codev.md) for full documentation.
 
@@ -54,14 +53,15 @@ See [codev.md](codev.md) for full documentation.
 
 | Command | Description |
 |---------|-------------|
-| `af start` | Start the architect dashboard |
-| `af stop` | Stop all agent farm processes |
+| `af dash start` | Start the architect dashboard |
+| `af dash stop` | Stop all agent farm processes |
 | `af spawn` | Spawn a new builder |
 | `af status` | Show status of all agents |
 | `af cleanup` | Clean up a builder worktree |
 | `af send` | Send instructions to a builder |
 | `af open` | Open file annotation viewer |
-| `af util` | Spawn a utility shell |
+| `af shell` | Spawn a utility shell |
+| `af tower` | Cross-project dashboard |
 
 See [agent-farm.md](agent-farm.md) for full documentation.
 
@@ -87,21 +87,11 @@ All codev commands support:
 
 ## Configuration
 
-Customize agent-farm commands via `codev/config.json`:
-
-```json
-{
-  "shell": {
-    "architect": "claude --model opus",
-    "builder": "claude --model sonnet",
-    "shell": "bash"
-  }
-}
-```
+Agent Farm is configured via `af-config.json` at the project root. Created during `codev init` or `codev adopt`. Override via CLI flags: `--architect-cmd`, `--builder-cmd`, `--shell-cmd`.
 
 ## Related Documentation
 
-- [SPIDER Protocol](../protocols/spider/protocol.md) - Multi-phase development workflow
+- [SPIR Protocol](../protocols/spir/protocol.md) - Multi-phase development workflow
 - [TICK Protocol](../protocols/tick/protocol.md) - Fast amendment workflow
 - [Architect Role](../roles/architect.md) - Architect responsibilities
 - [Builder Role](../roles/builder.md) - Builder responsibilities

package/skeleton/resources/workflow-reference.md

@@ -1,6 +1,6 @@
 # Architect-Builder Workflow Reference
 
-Quick reference for the 7-stage project workflow. For protocol details, see `codev/protocols/spider/protocol.md`.
+Quick reference for the 7-stage project workflow. For protocol details, see `codev/protocols/spir/protocol.md`.
 
 ## Workflow Overview
 
@@ -77,7 +77,7 @@ AI agents must stop and wait for human action at these gates.
 
 ```bash
 # Start the dashboard
-af start
+af dash start
 
 # Spawn a builder for a project
 af spawn -p 0044
@@ -95,7 +95,7 @@ af open codev/specs/0044-name.md
 af cleanup -p 0044
 
 # Stop everything
-af stop
+af dash stop
 ```
 
 ### Builder Commands
@@ -236,7 +236,7 @@ af cleanup -p XXXX --force
 
 ## Related Documentation
 
-- Full SPIDER protocol: `codev/protocols/spider/protocol.md`
+- Full SPIR protocol: `codev/protocols/spir/protocol.md`
 - Builder role: `codev/roles/builder.md`
 - Architect role: `codev/roles/architect.md`
 - Consultant role: `codev/roles/consultant.md`