Trim SKILL.md and prompt templates — reference CLI instead of duplicating

Replace static node/edge type tables and command examples with references
to lattice help concepts, lattice help workflows, and lattice --json.
Keep only behavioral rules (editing policy, workflow, gap filing) that
the CLI can't teach.

266 lines → 122 lines (54% reduction). No more manual updates needed
when node types or edge types change.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: gmoon

prompts/LATTICE_CLAUDE_MD.md

@@ -5,15 +5,11 @@ This project uses [Lattice](https://github.com/forkzero/lattice) for knowledge c
 ## Quick Reference
 
 ```bash
-lattice summary              # Status overview (nodes, resolution, drift)
+lattice summary              # Status overview
 lattice health               # Unified PASS/WARN/FAIL health check
-lattice list requirements    # All requirements
-lattice list messages        # All messages
-lattice get REQ-XXX-001      # Full details with edges
-lattice search -q "keyword"  # Text search
-lattice plan REQ-A REQ-B     # Implementation order
-lattice drift                # Check for stale edge bindings
 lattice help concepts        # Node types, edge semantics, versioning
+lattice help workflows       # Common task-oriented command sequences
+lattice help                 # Full grouped command list
 ```
 
 ## When Working on Features
@@ -23,23 +19,6 @@ lattice help concepts        # Node types, edge semantics, versioning
 3. **After completing**: `lattice resolve REQ-XXX-001 --verified`
 4. **Verify**: `lattice drift` to confirm no stale edges
 
-## Node Types
-
-| Type | Purpose | ID Pattern |
-|------|---------|------------|
-| Source | Research/references | `SRC-XXX` |
-| Thesis | Strategic claims (can be `contested`) | `THX-XXX` |
-| Requirement | Specifications | `REQ-XXX-NNN` |
-| Implementation | Code bindings | `IMP-XXX-NNN` |
-| Message | Persona-specific claims | `MSG-XXX-NNN` |
-
-## Key Edge Types
-
-- `supported_by`, `derives_from`, `satisfies`, `depends_on` (traceability)
-- `reveals_gap_in`, `challenges`, `validates` (feedback)
-- `rebuts`, `concedes` (adversarial debate)
-- `grounded_in` (message → thesis)
-
 ## Resolution States
 
 - `verified` - Implemented and tested

prompts/LATTICE_MCP_CLAUDE_MD.md

@@ -1,39 +1,24 @@
 # Lattice Integration (MCP)
 
-This project uses [Lattice](https://github.com/forkzero/lattice) for knowledge coordination via MCP. The `.lattice/` directory contains sources, theses, requirements, implementations, and messages connected by version-tracked edges.
+This project uses [Lattice](https://github.com/forkzero/lattice) for knowledge coordination via MCP.
 
 ## MCP Tools
 
 | Tool | Purpose |
 |------|---------|
-| `lattice_summary` | Status overview — nodes, resolution, drift, contested theses |
-| `lattice_search` | Find nodes by criteria (text, priority, resolution, tags) |
+| `lattice_summary` | Status overview — start here |
+| `lattice_search` | Find nodes by criteria |
 | `lattice_get` | Full node details with edges |
-| `lattice_list` | List nodes by type (sources, theses, requirements, implementations, messages) |
-| `lattice_resolve` | Mark requirement status (verified, blocked, deferred, wontfix) |
+| `lattice_list` | List nodes by type |
+| `lattice_resolve` | Mark requirement status |
 | `lattice_add_requirement` | Create new requirement |
 | `lattice_drift` | Check for stale edge bindings |
 
-## Node Types
-
-| Type | ID Pattern | Purpose |
-|------|-----------|---------|
-| Source | `SRC-*` | Research, papers, references |
-| Thesis | `THX-*` | Strategic claims (can be `contested`) |
-| Requirement | `REQ-*` | Testable specifications |
-| Implementation | `IMP-*` | Code that satisfies requirements |
-| Message | `MSG-*` | Persona-specific claims grounded in theses |
-
 ## Workflow
 
 1. **Start**: `lattice_summary` for current state
 2. **Find work**: `lattice_search` with `resolution: "unresolved"`
 3. **Get details**: `lattice_get` for full specification
 4. **Complete**: `lattice_resolve` with `status: "verified"`
 
-## Reference Requirements
-
-When implementing features, note the requirement ID in commits:
-```
-Implements REQ-XXX-001
-```
+Reference requirement IDs in commits: `Implements REQ-XXX-001`

skills/lattice/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: lattice
-description: "Lattice knowledge graph integration. Use when working in a project with a .lattice/ directory — for requirements, theses, sources, implementations, drift detection, or lattice CLI commands."
+description: "Lattice knowledge graph integration. Use when working in a project with a .lattice/ directory — for requirements, theses, sources, implementations, messages, drift detection, or lattice CLI commands."
 allowed-tools: Bash(lattice *), Bash(./target/release/lattice *), Bash(./target/debug/lattice *), Bash(gh issue *), Read, Grep, Glob
 ---
 
@@ -10,30 +10,14 @@ You have access to a **Lattice** knowledge graph in this project. The `.lattice/
 
 The key words MUST, MUST NOT, SHOULD, SHOULD NOT, and MAY in this document are to be interpreted as described in RFC 2119.
 
-## Quick Reference
+## Discovery
 
 ```bash
-# Health & Analysis
-lattice summary                  # Status overview (counts, drift, messages, contested)
-lattice health                   # Unified PASS/WARN/FAIL verdict
-lattice health --check           # CI gate — exits 2 on FAIL
-lattice drift                    # Check for stale edge bindings
-lattice freshness                # Check if lattice is updated alongside code
-lattice assess                   # Change pressure (contested theses, drift)
-lattice lint                     # Structural issues
-lattice plan REQ-A REQ-B         # Implementation order for requirements
-
-# Query
-lattice list requirements        # All requirements
-lattice list messages            # All messages
-lattice get REQ-XXX-001          # Full node details with edges
-lattice search -q "keyword"      # Text search (defaults to requirements)
-
-# Modify
-lattice edit REQ-XXX --title "..." # Edit node fields (auto-bumps version)
-lattice add edge --from IMP-XXX --type satisfies --to REQ-XXX  # Wire edges
-lattice remove edge --from IMP-XXX --type satisfies --to REQ-XXX
-lattice replace edge --from IMP-XXX --type satisfies --old-to REQ-OLD --new-to REQ-NEW
+lattice help                    # Grouped command list
+lattice help concepts           # Node types, edge semantics, versioning, ID conventions
+lattice help workflows          # Common task-oriented command sequences
+lattice <command> --help        # Help for any specific command
+lattice --json --compact        # Machine-readable command schema
 ```
 
 ## Editing Rules
@@ -43,7 +27,7 @@ The CLI handles timestamps, version bumps, edge wiring, and ID validation.
 
 If the CLI does not support a required operation, agents MAY edit `.lattice/` YAML files directly, but MUST run `lattice lint` immediately after to verify correctness.
 
-If a CLI gap is found, agents SHOULD file an issue on `forkzero/lattice` describing the missing capability:
+If a CLI gap is found, agents SHOULD file an issue on `forkzero/lattice`:
 ```bash
 gh issue create --repo forkzero/lattice \
   --title "CLI gap: <what's missing>" \
@@ -55,121 +39,29 @@ gh issue create --repo forkzero/lattice \
 
 ### Before Starting Work
 1. Run `lattice summary` to understand the current state
-2. Run `lattice plan` or `lattice search --priority P0 --resolution unresolved` to find what to work on
-3. Run `lattice get REQ-XXX` to read full requirement details before implementing
+2. Run `lattice health` to check overall lattice health
+3. Run `lattice plan` or `lattice search --priority P0 --resolution unresolved` to find what to work on
+4. Run `lattice get REQ-XXX` to read full requirement details before implementing
 
 ### While Working
 - Reference requirement IDs in commits: `Implements REQ-XXX-001`
 - Use `lattice get <ID> --format json` for structured data when you need to parse output
 
 ### After Completing Work
-- `lattice resolve REQ-XXX --verified` to mark requirements as done
-- `lattice verify IMP-XXX satisfies REQ-XXX --tests-pass` to record satisfaction evidence
-- If you implemented a new feature, add matching requirement(s) and resolve them as verified
-- `lattice edit IMP-XXX --body "updated description" --files "src/new.rs,src/lib.rs" --test-command "cargo test"` to update implementation nodes
-- `lattice add edge --from IMP-XXX --type satisfies --to REQ-XXX` to wire new edges
-- Run `lattice drift` to confirm no unresolved drift
+1. `lattice resolve REQ-XXX --verified` to mark requirements as done
+2. `lattice verify IMP-XXX satisfies REQ-XXX --tests-pass` to record satisfaction evidence
+3. `lattice edit IMP-XXX --files "src/new.rs" --test-command "cargo test"` to update implementation nodes
+4. `lattice add edge --from IMP-XXX --type satisfies --to REQ-XXX` to wire new edges
+5. Run `lattice drift` to confirm no unresolved drift
 
 ### If Gaps Are Found
 - `lattice refine REQ-XXX --gap-type missing_requirement --title "..." --description "..."` to create sub-requirements
 - `lattice add edge --from IMP-XXX --type reveals_gap_in --to REQ-XXX --rationale "..."` to record feedback
 
-## Node Types
-
-| Type | ID Pattern | Purpose |
-|------|-----------|---------|
-| Source | `SRC-XXX` | Research, papers, references |
-| Thesis | `THX-XXX` | Strategic claims backed by sources (can be `contested`) |
-| Requirement | `REQ-XXX-NNN` | Testable specifications derived from theses |
-| Implementation | `IMP-XXX-NNN` | Code that satisfies requirements |
-| Message | `MSG-XXX-NNN` | Persona-specific claims grounded in theses |
-
-## Edge Types
-
-| Edge | Direction | Meaning |
-|------|----------|---------|
-| `supported_by` | Thesis → Source | Evidence backing a claim |
-| `derives_from` | Requirement → Thesis | Specification from strategy |
-| `satisfies` | Implementation → Requirement | Code fulfills spec |
-| `depends_on` | Requirement → Requirement | Dependency ordering |
-| `reveals_gap_in` | Implementation → Requirement/Thesis | Discovered underspecification |
-| `challenges` | Any → Thesis | Contradictory evidence |
-| `validates` | Implementation → Thesis | Confirming evidence |
-| `rebuts` | Thesis → Thesis | Adversarial debate — direct counter-argument |
-| `concedes` | Thesis → Thesis | Partial agreement in debate |
-| `grounded_in` | Message → Thesis | Messaging claim traces to strategic position |
-
-## Resolution States
-
-- `verified` — Implemented and tested
-- `blocked` — Waiting on external dependency (with reason)
-- `deferred` — Postponed to later milestone (with reason)
-- `wontfix` — Rejected or out of scope (with reason)
-
-## Adding Nodes
-
-```bash
-lattice add requirement \
-  --id REQ-FEAT-001 --title "Short description" \
-  --body "Detailed specification" --priority P1 \
-  --category FEAT --derives-from THX-XXX --created-by "agent:claude"
-
-lattice add thesis \
-  --id THX-NEW --title "Claim" --body "Reasoning" \
-  --category technical --supported-by SRC-XXX --created-by "agent:claude"
-
-lattice add source \
-  --id SRC-NEW --title "Reference" --body "Summary" \
-  --url "https://..." --created-by "agent:claude"
-
-lattice add implementation \
-  --id IMP-FEAT-001 --title "Feature implementation" \
-  --body "Description of what was implemented" \
-  --language rust --files "src/main.rs,src/lib.rs" \
-  --test-command "cargo test" --satisfies REQ-FEAT-001 \
-  --created-by "agent:claude"
-
-lattice add message \
-  --id MSG-DEV-001 --title "Zero infrastructure" \
-  --body "File-based YAML, no servers needed" \
-  --persona developer --grounded-in THX-XXX \
-  --created-by "agent:claude"
-
-lattice add edge \
-  --from IMP-XXX --type validates --to THX-XXX \
-  --rationale "Implementation confirms thesis"
-```
-
-## Managing Edges
-
-```bash
-# Remove an edge
-lattice remove edge --from IMP-XXX --type satisfies --to REQ-XXX
-
-# Replace an edge target (retarget to a different node)
-lattice replace edge --from IMP-XXX --type satisfies \
-  --old-to REQ-OLD --new-to REQ-NEW --rationale "Requirement was split"
-```
-
-## Editing Nodes
-
-```bash
-lattice edit REQ-XXX --title "New title" --body "New body"
-lattice edit REQ-XXX --priority P0 --tags "core,storage"
-lattice edit IMP-XXX --files "src/new.rs,src/lib.rs" --test-command "cargo test"
-lattice edit IMP-XXX --body "Updated description" --status active
-```
-
-Agents MUST use `lattice edit` to modify existing nodes. The `edit` command auto-bumps the patch version and preserves all other fields. Type-specific flags: `--priority` (requirements only), `--files` and `--test-command` (implementations only).
-
 ## JSON Output
 
 All read and write commands accept `--format json` for structured output. Use this when you need to parse results programmatically.
 
-## Drift Detection
-
-Edges are version-bound. When a node is updated, edges referencing the old version become stale. Run `lattice drift` to detect these. Use `lattice drift --check` in CI (exits non-zero on drift).
-
 ## Product Owner Agent
 
 For backlog triage, strategic critique, and planning work, use the **product-owner** agent (`/product-owner`). It manages the lattice as persistent working memory for product strategy.