docs: add Gemini path fix (includeDirectories setting)

Gemini CLI can access ~/.claude/skills/ via:
  settings.json: { "context": { "includeDirectories": ["~/.claude/skills"] } }
  or CLI: gemini --include-directories ~/.claude/skills

Closes: skills-8nl, skills-bo8

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
dan 2026-01-09 19:35:28 -08:00
parent f7483edcf3
commit 8c033eedd1
2 changed files with 15 additions and 10 deletions

View file

@ -2,7 +2,7 @@
{"id":"skills-0nl","title":"Update orch skill to match CLI v0.1.0","description":"The orch skill (in ~/.claude/skills/orch/) is out of sync with the orch CLI.\n\nNeeded updates:\n- Fix model aliases: gpt-5 → gpt-5.2, claude-opus-4.1 → claude-opus-4.5\n- Add new aliases: deepseek, r1, qwen, qwen-fast, glm, sonar, sonar-pro\n- Document --synthesize flag for response aggregation\n- Document stdin piping support\n- Document orch models command\n- Document orch sessions command\n- Add --websearch, --serial, --allow-expensive options\n\nReference: ~/proj/orch/README.md and src/orch/models_registry.py","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-23T21:11:46.294285184-05:00","updated_at":"2025-12-24T01:29:54.408882125-05:00","closed_at":"2025-12-24T01:29:54.408882125-05:00","close_reason":"Updated skill with current CLI features and model aliases"}
{"id":"skills-0og","title":"spec-review: Define output capture and audit trail","description":"Reviews happen in terminal then disappear. No audit trail, no diffable history.\n\nAdd:\n- Guidance to tee output to review file (e.g., specs/{branch}/review.md)\n- Standard location for gate check results\n- Template for recording decisions and rationale","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-15T00:23:23.705164812-08:00","updated_at":"2025-12-15T13:02:32.313084337-08:00","closed_at":"2025-12-15T13:02:32.313084337-08:00"}
{"id":"skills-0tk","title":"Evaluate: jwz for transient agent state","description":"Evaluate jwz as complement to beads for agent coordination.\n\n## Current Understanding\n- beads: persistent issues (multi-session, dependencies)\n- jwz: transient messages (session coordination, async)\n\n## Questions to Answer\n1. Does jwz add value beyond what beads provides?\n2. Is the Zig dependency acceptable?\n3. Can we achieve same with simpler file-based approach?\n4. How does jwz handle multi-repo coordination?\n\n## Evaluation Criteria\n- Complexity vs benefit\n- Cross-agent compatibility\n- Git integration quality\n- Maintenance burden\n\n## Deliverable\nRecommendation: adopt jwz, build alternative, or extend beads","status":"open","priority":3,"issue_type":"task","created_at":"2026-01-09T19:01:44.672000734-08:00","created_by":"dan","updated_at":"2026-01-09T19:01:44.672000734-08:00"}
{"id":"skills-0u9","title":"Consolidate: Merge overlapping cross-agent design tasks","description":"Merge overlapping research/design tasks into coherent work items.\n\n## Current Overlap\n- skills-3gk: Research: Cross-agent hook alternatives\n- skills-3ja: Design: Cross-agent quality gate architecture \n- skills-thk: Design: Hybrid hook + gate architecture\n- skills-6fu: Research: State management for cross-agent workflows\n\nThese all touch the same problem space.\n\n## Proposed Consolidation\n1. Close overlapping tasks with \"consolidated\" reason\n2. Create single \"Design: Cross-agent enforcement architecture\" task\n3. Update epic description to reference consolidated task\n\n## Deliverable\nClean task list with no duplication","status":"open","priority":2,"issue_type":"task","created_at":"2026-01-09T19:32:57.364887317-08:00","created_by":"dan","updated_at":"2026-01-09T19:32:57.364887317-08:00"}
{"id":"skills-0u9","title":"Consolidate: Merge overlapping cross-agent design tasks","description":"Merge overlapping research/design tasks into coherent work items.\n\n## Current Overlap\n- skills-3gk: Research: Cross-agent hook alternatives\n- skills-3ja: Design: Cross-agent quality gate architecture \n- skills-thk: Design: Hybrid hook + gate architecture\n- skills-6fu: Research: State management for cross-agent workflows\n\nThese all touch the same problem space.\n\n## Proposed Consolidation\n1. Close overlapping tasks with \"consolidated\" reason\n2. Create single \"Design: Cross-agent enforcement architecture\" task\n3. Update epic description to reference consolidated task\n\n## Deliverable\nClean task list with no duplication","status":"closed","priority":2,"issue_type":"task","created_at":"2026-01-09T19:32:57.364887317-08:00","created_by":"dan","updated_at":"2026-01-09T19:33:42.464968954-08:00","closed_at":"2026-01-09T19:33:42.464968954-08:00","close_reason":"Created skills-8sj, closed 4 overlapping tasks"}
{"id":"skills-17f","title":"Ensure git access to both local Forgejo and ops-jrz1 Forgejo","description":"Need reliable access to both git servers for plugin development and deployment:\n\n**Local Forgejo (home):**\n- URL: http://192.168.1.108:3000\n- Currently down/unreachable at times\n- Used for skills repo remote\n\n**ops-jrz1 Forgejo (VPS):**\n- URL: https://git.clarun.xyz\n- Production server\n- Target for emes plugin deployment\n\n**Tasks:**\n- Verify local Forgejo is running (systemctl status)\n- Add ops-jrz1 as additional remote for skills repo\n- Consider mirroring skills repo to both\n- Document which forge is source of truth","status":"closed","priority":2,"issue_type":"task","created_at":"2026-01-09T11:14:52.639492685-08:00","created_by":"dan","updated_at":"2026-01-09T16:57:16.417563927-08:00","closed_at":"2026-01-09T16:57:16.417563927-08:00","close_reason":"Multi-push configured: origin pushes to both local and clarun Forgejos"}
{"id":"skills-1ig","title":"Brainstorm agent-friendly doc conventions","description":"# Agent-Friendly Doc Conventions - Hybrid Architecture\n\n## FINAL ARCHITECTURE: Vale + LLM Hybrid\n\n### Insight\n\u003e \"Good old deterministic testing (dumb robots) is the best way to keep in check LLMs (smart robots) at volume.\"\n\n### Split by Tool\n\n| Category | Rubrics | Tool |\n|----------|---------|------|\n| Vale-only | Format Integrity, Deterministic Instructions, Terminology Strictness, Token Efficiency | Fast, deterministic, CI-friendly |\n| Vale + LLM | Semantic Headings, Configuration Precision, Security Boundaries | Vale flags, LLM suggests fixes |\n| LLM-only | Contextual Independence, Code Executability, Execution Verification | Semantic understanding required |\n\n### Pipeline\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ Stage 1: Vale (deterministic, fast, free) │\n│ - Runs in CI on every commit │\n│ - Catches 40% of issues instantly │\n│ - No LLM cost for clean docs │\n└─────────────────────┬───────────────────────────────────────┘\n │ only if Vale passes\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ Stage 2: LLM Triage (cheap model) │\n│ - Evaluates 3 semantic rubrics │\n│ - Identifies which need patches │\n└─────────────────────┬───────────────────────────────────────┘\n │ only if issues found\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ Stage 3: LLM Specialists (capable model) │\n│ - One agent per failed rubric │\n│ - Generates patches │\n└─────────────────────────────────────────────────────────────┘\n```\n\n### Why This Works\n- Vale is battle-tested, fast, CI-native\n- LLM only fires when needed (adaptive cost)\n- Deterministic rules catch predictable issues\n- LLM handles semantic/contextual issues\n\n---\n\n## Vale Rules Needed\n\n### Format Integrity\n- Existence: code blocks without language tags\n- Regex for unclosed fences\n\n### Deterministic Instructions \n- Existence: hedging words (\"might\", \"may want to\", \"consider\", \"you could\")\n\n### Terminology Strictness\n- Consistency: flag term variations\n\n### Token Efficiency\n- Existence: filler phrases (\"In this section we will...\", \"As you may know...\")\n\n### Semantic Headings (partial)\n- Existence: banned headings (\"Overview\", \"Introduction\", \"Getting Started\")\n\n### Configuration Precision (partial)\n- Existence: vague versions (\"Python 3.x\", \"recent version\")\n\n### Security Boundaries (partial)\n- Existence: hardcoded API key patterns\n\n---\n\n## NEXT STEPS\n\n1. Create Vale style for doc-review rubrics\n2. Test Vale on sample docs\n3. Design LLM prompts for semantic rubrics only\n4. Wire into orch or standalone","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-04T14:02:04.898026177-08:00","updated_at":"2025-12-04T16:43:53.0608948-08:00","closed_at":"2025-12-04T16:43:53.0608948-08:00"}
{"id":"skills-1ks","title":"Dual-publish pattern: Convert remaining skills","description":"Convert skills to dual-publish pattern (Nix + Claude plugin):\n\n**Pattern established with orch:**\n- Keep SKILL.md at root (Nix deployment)\n- Add .claude-plugin/plugin.json (Claude marketplace)\n- Copy to skills/\u003cname\u003e.md (Claude auto-discovery)\n\n**Skills to convert:**\n- [ ] worklog\n- [ ] code-review (has lenses dependency)\n- [ ] ops-review (has lenses dependency)\n- [ ] playwright-visit\n- [ ] screenshot-latest\n- [ ] niri-window-capture\n- [ ] web-search\n- [ ] web-research\n\n**Why dual-publish:**\n- Cross-agent support (Gemini, OpenCode can't use Claude plugins)\n- Nix provides system-level deployment\n- Claude plugin system provides hooks, marketplace discovery\n- See skills-bo8 for Gemini path restriction issue","status":"closed","priority":2,"issue_type":"task","created_at":"2026-01-09T11:20:47.271151803-08:00","created_by":"dan","updated_at":"2026-01-09T16:19:13.995523596-08:00","closed_at":"2026-01-09T16:19:13.995523596-08:00","close_reason":"All 16 skills converted to dual-publish pattern"}
@ -14,10 +14,10 @@
{"id":"skills-2xo","title":"Add README.md for web-search skill","description":"web-search skill has SKILL.md and scripts but no README.md. AGENTS.md says README.md is for humans, contains installation instructions, usage examples, prerequisites.","status":"closed","priority":2,"issue_type":"task","created_at":"2025-11-30T11:58:14.26066025-08:00","updated_at":"2025-12-28T22:37:48.324822157-05:00","closed_at":"2025-12-28T22:37:48.324822157-05:00","close_reason":"Added README.md with prerequisites, usage examples, and cross-references","dependencies":[{"issue_id":"skills-2xo","depends_on_id":"skills-vb5","type":"blocks","created_at":"2025-11-30T12:01:30.240439018-08:00","created_by":"daemon","metadata":"{}"}]}
{"id":"skills-39g","title":"RFC: .skills manifest pattern for per-repo skill deployment","description":"Document the .skills file pattern where projects declare skills in a manifest, .envrc reads it, and agents can query/edit it.","status":"closed","priority":2,"issue_type":"feature","created_at":"2025-11-30T12:37:50.106992381-08:00","updated_at":"2025-11-30T12:43:04.155161727-08:00","closed_at":"2025-11-30T12:43:04.155161727-08:00"}
{"id":"skills-3em","title":"Prototype elevation pipeline","description":"Build pipeline: successful molecule → skill draft\n1. On molecule close, option to 'elevate'\n2. Analyze squashed trace\n3. Extract generalizable pattern\n4. Generate SKILL.md draft\n5. Human approval gate\n\nStart simple: script that takes squashed molecule ID and outputs draft SKILL.md\n\nMigrated from dotfiles-2p2.","status":"closed","priority":3,"issue_type":"task","created_at":"2025-12-23T19:21:08.208885336-05:00","updated_at":"2025-12-29T13:55:35.80560789-05:00","closed_at":"2025-12-29T13:55:35.80560789-05:00","close_reason":"Parked with ADR-001: skills-molecules integration deferred. Current simpler approach (skills as standalone) works well. Revisit when complex orchestration needed.","dependencies":[{"issue_id":"skills-3em","depends_on_id":"skills-jeb","type":"blocks","created_at":"2025-12-23T19:21:50.034640219-05:00","created_by":"dan"},{"issue_id":"skills-3em","depends_on_id":"skills-2k0","type":"blocks","created_at":"2025-12-23T19:50:10.516122892-05:00","created_by":"daemon"}]}
{"id":"skills-3gk","title":"Research: Cross-agent hook alternatives","description":"Claude Code has hooks (Stop, SessionStart, etc.) for mechanical enforcement. Other agents don't.\n\nResearch alternatives for cross-agent quality gates:\n\n1. **External wrapper** - Script that launches agent, monitors output, gates exit\n2. **Protocol-based** - Agent follows instructions in AGENTS.md, posts to state store\n3. **Orchestrator pattern** - Meta-agent spawns worker + reviewer, enforces gate\n4. **Hybrid** - Hooks where available, protocol elsewhere\n\nEvaluate:\n- Enforcement strength (mechanical vs cooperative)\n- Implementation complexity\n- Agent compatibility\n- Failure modes\n\nOutput: Comparison doc with recommendation","status":"open","priority":2,"issue_type":"task","created_at":"2026-01-09T17:14:20.433319252-08:00","created_by":"dan","updated_at":"2026-01-09T17:14:20.433319252-08:00"}
{"id":"skills-3ja","title":"Design: Cross-agent quality gate architecture","description":"Design a quality gate pattern that works regardless of agent.\n\nRequirements:\n- Worker agent can be Claude, Gemini, OpenCode, etc.\n- Reviewer agent can be any capable model\n- Gate blocks completion until reviewer approves\n- Circuit breakers prevent infinite loops\n- Works in autonomous/unattended scenarios\n\nBuilding on alice/idle research (docs/research/idle-alice-quality-gate.md):\n- alice uses Claude hooks + jwz state\n- We need agent-agnostic equivalent\n\nConsiderations:\n- State management: jwz vs beads vs simple files\n- Enforcement: mechanical vs protocol-based\n- Reviewer selection: orch consensus vs single model\n- Activation: opt-in prefix vs context-based\n\nOutput: Architecture doc with component design","status":"open","priority":2,"issue_type":"task","created_at":"2026-01-09T17:14:20.657906484-08:00","created_by":"dan","updated_at":"2026-01-09T17:14:20.657906484-08:00"}
{"id":"skills-3gk","title":"Research: Cross-agent hook alternatives","description":"Claude Code has hooks (Stop, SessionStart, etc.) for mechanical enforcement. Other agents don't.\n\nResearch alternatives for cross-agent quality gates:\n\n1. **External wrapper** - Script that launches agent, monitors output, gates exit\n2. **Protocol-based** - Agent follows instructions in AGENTS.md, posts to state store\n3. **Orchestrator pattern** - Meta-agent spawns worker + reviewer, enforces gate\n4. **Hybrid** - Hooks where available, protocol elsewhere\n\nEvaluate:\n- Enforcement strength (mechanical vs cooperative)\n- Implementation complexity\n- Agent compatibility\n- Failure modes\n\nOutput: Comparison doc with recommendation","status":"closed","priority":2,"issue_type":"task","created_at":"2026-01-09T17:14:20.433319252-08:00","created_by":"dan","updated_at":"2026-01-09T19:33:36.683960774-08:00","closed_at":"2026-01-09T19:33:36.683960774-08:00","close_reason":"Consolidated into skills-8sj"}
{"id":"skills-3ja","title":"Design: Cross-agent quality gate architecture","description":"Design a quality gate pattern that works regardless of agent.\n\nRequirements:\n- Worker agent can be Claude, Gemini, OpenCode, etc.\n- Reviewer agent can be any capable model\n- Gate blocks completion until reviewer approves\n- Circuit breakers prevent infinite loops\n- Works in autonomous/unattended scenarios\n\nBuilding on alice/idle research (docs/research/idle-alice-quality-gate.md):\n- alice uses Claude hooks + jwz state\n- We need agent-agnostic equivalent\n\nConsiderations:\n- State management: jwz vs beads vs simple files\n- Enforcement: mechanical vs protocol-based\n- Reviewer selection: orch consensus vs single model\n- Activation: opt-in prefix vs context-based\n\nOutput: Architecture doc with component design","status":"closed","priority":2,"issue_type":"task","created_at":"2026-01-09T17:14:20.657906484-08:00","created_by":"dan","updated_at":"2026-01-09T19:33:36.694607649-08:00","closed_at":"2026-01-09T19:33:36.694607649-08:00","close_reason":"Consolidated into skills-8sj"}
{"id":"skills-3o7","title":"Fix ai-skills.nix missing sha256 hash","description":"modules/ai-skills.nix:16 has empty sha256 placeholder for opencode-skills npm package. Either get actual hash or remove/comment out the incomplete fetchFromNpm approach.","status":"closed","priority":2,"issue_type":"bug","created_at":"2025-11-30T11:58:24.404929863-08:00","updated_at":"2025-11-30T12:12:39.372107348-08:00","closed_at":"2025-11-30T12:12:39.372107348-08:00"}
{"id":"skills-4fe","title":"Reframe: Epic around abstract layers (not tools)","description":"Reframe skills-hf1 epic around concepts, not implementations.\n\n## Abstract Layers\n\n| Layer | Concept | Purpose |\n|-------|---------|---------|\n| **Message Passing** | Async agent coordination | Session handoffs, status updates |\n| **Memory** | Persistent work items | Issues, dependencies, review state |\n| **Enforcement** | Quality gates | Block completion until approved |\n\n## Current Problem\nEpic references specific tools (jwz, beads, hooks) rather than concepts.\nMakes it hard to swap implementations.\n\n## Proposed Changes\n1. Update epic description with layer abstractions\n2. Define interface requirements for each layer\n3. Note current implementations as examples, not requirements\n\n## Deliverable\nUpdated epic with tool-agnostic framing","status":"open","priority":2,"issue_type":"task","created_at":"2026-01-09T19:32:57.483804644-08:00","created_by":"dan","updated_at":"2026-01-09T19:32:57.483804644-08:00"}
{"id":"skills-4fe","title":"Reframe: Epic around abstract layers (not tools)","description":"Reframe skills-hf1 epic around concepts, not implementations.\n\n## Abstract Layers\n\n| Layer | Concept | Purpose |\n|-------|---------|---------|\n| **Message Passing** | Async agent coordination | Session handoffs, status updates |\n| **Memory** | Persistent work items | Issues, dependencies, review state |\n| **Enforcement** | Quality gates | Block completion until approved |\n\n## Current Problem\nEpic references specific tools (jwz, beads, hooks) rather than concepts.\nMakes it hard to swap implementations.\n\n## Proposed Changes\n1. Update epic description with layer abstractions\n2. Define interface requirements for each layer\n3. Note current implementations as examples, not requirements\n\n## Deliverable\nUpdated epic with tool-agnostic framing","status":"closed","priority":2,"issue_type":"task","created_at":"2026-01-09T19:32:57.483804644-08:00","created_by":"dan","updated_at":"2026-01-09T19:34:10.530947162-08:00","closed_at":"2026-01-09T19:34:10.530947162-08:00","close_reason":"Epic skills-hf1 reframed around abstract layers"}
{"id":"skills-4pw","title":"spec-review: Expand NFR checklist in prompts","description":"Current prompts mention 'performance, security, accessibility' but miss many critical NFRs.\n\nExpand to include:\n- Security (authn/authz, secrets, threat model)\n- Privacy/compliance (GDPR, PII)\n- Observability (logging, metrics, tracing)\n- Reliability (SLOs, failure modes)\n- Rollout/rollback strategy\n- Migration/backfill\n- Data retention/lifecycle\n- Cost constraints","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-15T00:23:24.485420922-08:00","updated_at":"2025-12-15T14:03:46.508452685-08:00","closed_at":"2025-12-15T14:03:46.508452685-08:00"}
{"id":"skills-4u0","title":"Skills + Molecules Integration","description":"Integrate skills system with beads molecules.\n\nKey concepts from consensus brainstorm:\n1. Skills = procedural knowledge (HOW), Molecules = work tracking (WHAT)\n2. Link via skill: field in molecule nodes\n3. Wisps as execution traces for debugging/replay\n4. Elevation pipeline: successful molecule → auto-generate skill draft\n5. Skills as transition middleware (on_enter/on_exit hooks)\n\nImplementation phases:\n- Phase 1: Document findings (ADR)\n- Phase 2: Wisp execution trace format\n- Phase 3: Elevation pipeline prototype\n- Phase 4: Test on real skill (worklog)\n\nMigrated from dotfiles-jjb.","status":"closed","priority":2,"issue_type":"feature","created_at":"2025-12-23T19:20:19.818455543-05:00","updated_at":"2025-12-29T13:55:35.782406912-05:00","closed_at":"2025-12-29T13:55:35.782406912-05:00","close_reason":"Parked with ADR-001: skills-molecules integration deferred. Current simpler approach (skills as standalone) works well. Revisit when complex orchestration needed.","dependencies":[{"issue_id":"skills-4u0","depends_on_id":"skills-rex","type":"blocks","created_at":"2025-12-23T19:22:10.725578029-05:00","created_by":"dan"},{"issue_id":"skills-4u0","depends_on_id":"skills-vpy","type":"blocks","created_at":"2025-12-23T19:23:18.166650023-05:00","created_by":"dan"},{"issue_id":"skills-4u0","depends_on_id":"skills-u3d","type":"blocks","created_at":"2025-12-23T19:23:28.59360697-05:00","created_by":"dan"}]}
{"id":"skills-4yn","title":"Decide on screenshot-latest skill deployment","description":"DEPLOYED.md shows screenshot-latest as 'Not yet deployed - Pending decision'. Low risk skill that finds existing files. Need to decide whether to deploy or archive.","status":"closed","priority":2,"issue_type":"task","created_at":"2025-11-30T11:58:33.099790809-08:00","updated_at":"2025-12-28T20:55:18.515543619-05:00","closed_at":"2025-12-28T20:55:18.515543619-05:00","close_reason":"Decided to deploy - low risk, useful for avoiding path typing. Added to dotfiles claude.nix."}
@ -29,7 +29,7 @@
{"id":"skills-5vg","title":"spec-review: Add context/assumptions step to prompts","description":"Reviews can become speculative without establishing context first.\n\nAdd to prompts:\n- List assumptions being made\n- Distinguish: missing from doc vs implied vs out of scope\n- Ask clarifying questions if critical context missing","status":"closed","priority":3,"issue_type":"task","created_at":"2025-12-15T00:23:25.681448596-08:00","updated_at":"2025-12-15T14:06:15.415750911-08:00","closed_at":"2025-12-15T14:06:15.415750911-08:00"}
{"id":"skills-6ae","title":"Create ui-query skill for AT-SPI integration","description":"Create a skill that provides programmatic UI tree access via AT-SPI.\n\n## Context\nAT-SPI is now enabled in dotfiles (services.gnome.at-spi2-core + QT_LINUX_ACCESSIBILITY_ALWAYS_ON).\nThis complements niri-window-capture (visual) with semantic UI data.\n\n## Capabilities\n- Read text from GTK/Qt widgets directly (no OCR)\n- Find UI elements by role (button, text-field, menu)\n- Query element states (focused, enabled, checked)\n- Get element positions for potential input simulation\n- Navigate parent/child relationships\n\n## Suggested structure\nskills/ui-query/\n├── SKILL.md\n├── scripts/\n│ ├── list-windows.py # Windows with AT-SPI info\n│ ├── get-text.py # Extract text from window/element\n│ ├── find-element.py # Find by role/name\n│ └── query-state.py # Element states\n└── README.md\n\n## Notes\n- Start simple: list windows, get text\n- pyatspi available via python3Packages.pyatspi\n- Use accerciser (now installed) to explore the tree","status":"open","priority":2,"issue_type":"feature","created_at":"2025-12-29T15:37:55.592793763-05:00","created_by":"dan","updated_at":"2025-12-29T15:37:55.592793763-05:00"}
{"id":"skills-6e3","title":"Searchable Claude Code conversation history","description":"## Context\nClaude Code persists full conversations in `~/.claude/projects/\u003cproject\u003e/\u003cuuid\u003e.jsonl`. This is complete but not searchable - can't easily find \"that session where we solved X\".\n\n## Goal\nMake conversation history searchable without requiring manual worklogs.\n\n## Approach\n\n### Index structure\n```\n~/.claude/projects/\u003cproject\u003e/\n \u003cuuid\u003e.jsonl # raw conversation (existing)\n index.jsonl # session metadata + summaries (new)\n```\n\n### Index entry format\n```json\n{\n \"uuid\": \"f9a4c161-...\",\n \"date\": \"2025-12-17\",\n \"project\": \"/home/dan/proj/skills\",\n \"summary\": \"Explored Wayland desktop automation, AT-SPI investigation, vision model benchmark\",\n \"keywords\": [\"wayland\", \"niri\", \"at-spi\", \"automation\", \"seeing-problem\"],\n \"commits\": [\"906f2bc\", \"0b97155\"],\n \"duration_minutes\": 90,\n \"message_count\": 409\n}\n```\n\n### Features needed\n1. **Index builder** - Parse JSONL, extract/generate summary + keywords\n2. **Search CLI** - `claude-search \"AT-SPI wayland\"` → matching sessions\n3. **Auto-index hook** - Update index on session end or compaction\n\n## Questions\n- Generate summaries via AI or extract heuristically?\n- Index per-project or global?\n- How to handle very long sessions (multiple topics)?\n\n## Value\n- Find past solutions without remembering dates\n- Model reflection: include relevant past sessions in context\n- Replace manual worklogs with auto-generated metadata","status":"closed","priority":2,"issue_type":"feature","created_at":"2025-12-17T15:56:50.913766392-08:00","updated_at":"2025-12-29T18:35:56.530154004-05:00","closed_at":"2025-12-29T18:35:56.530154004-05:00","close_reason":"Prototype complete: bin/claude-search indexes 122 sessions, searches by keyword. Future: auto-index hook, full-text search, keyword extraction."}
{"id":"skills-6fu","title":"Research: State management for cross-agent workflows","description":"Evaluate state management options for cross-agent coordination.\n\nOptions:\n1. **jwz** - emes tool, append-only JSONL, git-mergeable, Zig\n2. **beads** - Our tool, graph-based issues, Rust\n3. **Simple files** - JSON/JSONL in .state/ directory\n4. **Environment variables** - Ephemeral session state\n\nCriteria:\n- Cross-agent access (all can read/write via CLI)\n- Git compatibility (mergeable, not conflicting)\n- Persistence (session vs permanent)\n- Query capability (search, filter)\n- Complexity (dependencies, setup)\n\nContext:\n- beads for persistent issues/work\n- jwz for transient session coordination\n- May need both for different purposes\n\nOutput: Recommendation on state management strategy","status":"open","priority":3,"issue_type":"task","created_at":"2026-01-09T17:14:20.971160754-08:00","created_by":"dan","updated_at":"2026-01-09T17:14:20.971160754-08:00"}
{"id":"skills-6fu","title":"Research: State management for cross-agent workflows","description":"Evaluate state management options for cross-agent coordination.\n\nOptions:\n1. **jwz** - emes tool, append-only JSONL, git-mergeable, Zig\n2. **beads** - Our tool, graph-based issues, Rust\n3. **Simple files** - JSON/JSONL in .state/ directory\n4. **Environment variables** - Ephemeral session state\n\nCriteria:\n- Cross-agent access (all can read/write via CLI)\n- Git compatibility (mergeable, not conflicting)\n- Persistence (session vs permanent)\n- Query capability (search, filter)\n- Complexity (dependencies, setup)\n\nContext:\n- beads for persistent issues/work\n- jwz for transient session coordination\n- May need both for different purposes\n\nOutput: Recommendation on state management strategy","status":"closed","priority":3,"issue_type":"task","created_at":"2026-01-09T17:14:20.971160754-08:00","created_by":"dan","updated_at":"2026-01-09T19:33:36.714686046-08:00","closed_at":"2026-01-09T19:33:36.714686046-08:00","close_reason":"Consolidated into skills-8sj"}
{"id":"skills-6gw","title":"Add artifact provenance to traces","description":"Current: files_created lists paths only.\nProblem: Can't detect regressions or validate outputs.\n\nAdd:\n- Content hash (sha256)\n- File size\n- For modifications: git_diff_summary (files changed, line counts)\n\nExample:\n outputs:\n artifacts:\n - path: docs/worklogs/...\n sha256: abc123...\n size: 1234\n action: created|modified\n\nEnables: diff traces, regression testing, validation.","status":"closed","priority":3,"issue_type":"task","created_at":"2025-12-23T19:49:48.654952533-05:00","updated_at":"2025-12-29T13:55:35.827778174-05:00","closed_at":"2025-12-29T13:55:35.827778174-05:00","close_reason":"Parked with ADR-001: skills-molecules integration deferred. Current simpler approach (skills as standalone) works well. Revisit when complex orchestration needed."}
{"id":"skills-6jw","title":"spec-review: Add severity labeling to prompts and reviews","description":"Reviews produce flat lists mixing blockers with minor nits. Hard to make decisions.\n\nAdd to prompts:\n- Require severity labels: Blocker / High / Medium / Low\n- Sort output by severity\n- Include impact and likelihood for each issue","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-15T00:23:23.334156366-08:00","updated_at":"2025-12-15T13:00:32.678573181-08:00","closed_at":"2025-12-15T13:00:32.678573181-08:00"}
{"id":"skills-6x1","title":"Epic: emes plugin architecture alignment","description":"Convert skills to emes-style plugin architecture for portability across Claude Code, Gemini, and VPS deployment (ops-jrz1).\n\n**emes tools (evil-mind-evil-sword org):**\n- tissue: Git-native issue tracking (machine-first)\n- idle: Quality gate (blocks exit until reviewer approves)\n- jwz: Async messaging with identity/git context\n- marketplace: Plugin distribution registry\n\n**Conversion work:**\n1. Add .claude-plugin/plugin.json to each skill\n2. Restructure: SKILL.md → skills/\u003cname\u003e.md (auto-discovery)\n3. Add hooks/ where applicable (quality gates)\n4. Create marketplace.json registry\n5. Test with ops-jrz1 deployment\n\n**Key principles from emes:**\n- Pull context on-demand (not big upfront injections)\n- Mechanical enforcement via hooks (not prompts)\n- References over inline content\n- Machine-first interfaces (JSON output)\n\n**Candidates for conversion:**\n- orch (simple CLI wrapper)\n- worklog (scripts + templates)\n- code-review (has lenses, might want hooks)\n- ops-review (same pattern)","status":"closed","priority":2,"issue_type":"epic","created_at":"2026-01-09T10:59:12.291560832-08:00","created_by":"dan","updated_at":"2026-01-09T17:14:41.429380141-08:00","closed_at":"2026-01-09T17:14:41.429380141-08:00","close_reason":"Dual-publish complete. Ongoing cross-agent work continues under skills-hf1"}
@ -40,7 +40,8 @@
{"id":"skills-8d4","title":"Compare CLI_REFERENCE.md with upstream","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-03T20:15:53.268324087-08:00","updated_at":"2025-12-03T20:17:26.552616779-08:00","closed_at":"2025-12-03T20:17:26.552616779-08:00","dependencies":[{"issue_id":"skills-8d4","depends_on_id":"skills-ebh","type":"discovered-from","created_at":"2025-12-03T20:15:53.27265681-08:00","created_by":"daemon","metadata":"{}"}]}
{"id":"skills-8d9","title":"Add conversational patterns to orch skill","description":"## Context\nThe orch skill currently documents consensus and single-shot chat, but doesn't\nteach agents how to use orch for multi-turn conversations with external AIs.\n\n## Goal\nAdd documentation and patterns for agent-driven conversations where the calling\nagent (Claude Code) orchestrates multi-turn dialogues using orch primitives.\n\n## Patterns to document\n\n### Session-based multi-turn\n```bash\n# Initial query\nRESPONSE=$(orch chat \"Analyze this\" --model claude --format json)\nSESSION=$(echo \"$RESPONSE\" | jq -r .session_id)\n\n# Continue conversation\norch chat \"Elaborate on X\" --model claude --session $SESSION\n\n# Inspect state\norch sessions info $SESSION\norch sessions show $SESSION --last 2 --format text\n```\n\n### Cross-model dialogue\n```bash\n# Get one model's take\nCLAUDE=$(orch chat \"Review this\" --model claude --format json)\nCLAUDE_SAYS=$(echo \"$CLAUDE\" | jq -r '.responses[0].content')\n\n# Ask another model to respond\norch chat \"Claude said: $CLAUDE_SAYS\n\nWhat's your perspective?\" --model gemini\n```\n\n### When to use conversations vs consensus\n- Consensus: quick parallel opinions on a decision\n- Conversation: deeper exploration, follow-up questions, iterative refinement\n\n## Files\n- skills/orch/SKILL.md\n\n## Related\n- orch-c3r: Design: Session introspection for agent-driven conversations (in orch repo)","status":"closed","priority":2,"issue_type":"feature","created_at":"2025-12-18T19:57:28.201494288-08:00","updated_at":"2025-12-29T15:34:16.254181578-05:00","closed_at":"2025-12-29T15:34:16.254181578-05:00","close_reason":"Added conversational patterns section to orch SKILL.md: sessions, cross-model dialogue, iterative refinement, consensus vs chat guidance."}
{"id":"skills-8ma","title":"worklog skill: remove org-mode references, use markdown instead","description":"The worklog skill currently references org-mode format (.org files) in the template and instructions. Update to use markdown (.md) instead:\n\n1. Update ~/.claude/skills/worklog/templates/worklog-template.org → worklog-template.md\n2. Convert org-mode syntax to markdown (#+TITLE → # Title, * → ##, etc.)\n3. Update skill instructions to reference .md files\n4. Update suggest-filename.sh to output .md extension\n\nContext: org-mode is less widely supported than markdown in tooling and editors.","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-31T08:43:55.761429693-05:00","created_by":"dan","updated_at":"2026-01-02T00:13:05.338810905-05:00","closed_at":"2026-01-02T00:13:05.338810905-05:00","close_reason":"Migrated worklog skill from org-mode to markdown. Template, scripts, and SKILL.md updated. Backward compatible with existing .org files."}
{"id":"skills-8nl","title":"Fix: Gemini path restrictions for skills (skills-bo8)","description":"Concrete fix for Gemini not reading ~/.claude/skills/.\n\n## Problem\nGemini's ReadFile tool restricts to workspace directories.\nSymlinked ~/.claude/skills/ is blocked.\n\n## Options\n\n### A: Copy skills into workspace\n- Add skills/ to project repos\n- Pro: Works immediately\n- Con: Duplication, sync issues\n\n### B: Shell workaround in skill\n- Use \\`cat\\` instead of ReadFile\n- Pro: No duplication\n- Con: Fragile, skill must know about limitation\n\n### C: Configure Gemini allowed paths\n- Research if Gemini has path config\n- Pro: Clean solution\n- Con: May not exist\n\n### D: MCP server for skills\n- Skills exposed via MCP\n- Pro: Agent-agnostic\n- Con: Complexity, user said not interested in MCP\n\n## Deliverable\nWorking solution for Gemini to read skills","status":"open","priority":2,"issue_type":"task","created_at":"2026-01-09T19:32:57.683370528-08:00","created_by":"dan","updated_at":"2026-01-09T19:32:57.683370528-08:00"}
{"id":"skills-8nl","title":"Fix: Gemini path restrictions for skills (skills-bo8)","description":"Concrete fix for Gemini not reading ~/.claude/skills/.\n\n## Problem\nGemini's ReadFile tool restricts to workspace directories.\nSymlinked ~/.claude/skills/ is blocked.\n\n## Options\n\n### A: Copy skills into workspace\n- Add skills/ to project repos\n- Pro: Works immediately\n- Con: Duplication, sync issues\n\n### B: Shell workaround in skill\n- Use \\`cat\\` instead of ReadFile\n- Pro: No duplication\n- Con: Fragile, skill must know about limitation\n\n### C: Configure Gemini allowed paths\n- Research if Gemini has path config\n- Pro: Clean solution\n- Con: May not exist\n\n### D: MCP server for skills\n- Skills exposed via MCP\n- Pro: Agent-agnostic\n- Con: Complexity, user said not interested in MCP\n\n## Deliverable\nWorking solution for Gemini to read skills","status":"closed","priority":2,"issue_type":"task","created_at":"2026-01-09T19:32:57.683370528-08:00","created_by":"dan","updated_at":"2026-01-09T19:35:28.05552467-08:00","closed_at":"2026-01-09T19:35:28.05552467-08:00","close_reason":"Fix found: Gemini includeDirectories setting"}
{"id":"skills-8sj","title":"Design: Cross-agent enforcement architecture","description":"Unified design for cross-agent quality gates and coordination.\n\nConsolidates: skills-3gk, skills-3ja, skills-thk, skills-6fu\n\n## Abstract Layers\n\n### 1. Message Passing Layer\n- **Purpose:** Async agent coordination, session handoffs\n- **Interface:** post(topic, message), read(topic), reply(id, message)\n- **Requirements:** Append-only, git-mergeable, agent-attributed\n\n### 2. Memory Layer \n- **Purpose:** Persistent work items, review state\n- **Interface:** create(issue), update(id, state), query(filters)\n- **Requirements:** Cross-session, dependency tracking, searchable\n\n### 3. Enforcement Layer\n- **Purpose:** Quality gates, completion blocking\n- **Interface:** check_gate(session) -\u003e allow/block, register_reviewer(session)\n\n## Enforcement Strategies\n\n| Agent | Mechanism | Strength |\n|-------|-----------|----------|\n| Claude Code | Stop hook | Mechanical |\n| Gemini CLI | Stop hook | Mechanical |\n| OpenCode | Orchestrator | Protocol |\n| Codex | Orchestrator | Protocol |\n| Any | Wrapper script | External |\n\n## State Schema\n\n```\nreview_state:\n session_id: string\n status: pending | in_review | approved | rejected\n worker_agent: string\n reviewer_agent: string\n issues_found: [issue_ids]\n approved_at: timestamp\n```\n\n## Circuit Breakers\n- Semantic drift detection\n- Three-strike tool failures \n- Budget/time limits\n\n## Deliverables\n1. Architecture diagram\n2. Interface definitions\n3. State schema\n4. Hook configuration templates\n5. Orchestrator flow pseudocode","status":"open","priority":2,"issue_type":"task","created_at":"2026-01-09T19:33:31.801684987-08:00","created_by":"dan","updated_at":"2026-01-09T19:33:31.801684987-08:00"}
{"id":"skills-8v0","title":"Consolidate skill list definitions (flake.nix + ai-skills.nix)","description":"Skill list duplicated in:\n- flake.nix (lines 15-27)\n- modules/ai-skills.nix (lines 8-18)\n\nIssues:\n- Manual sync required when adding skills\n- No validation that referenced skills exist\n\nFix:\n- Single source of truth for skill list\n- Consider generating one from the other\n\nSeverity: MEDIUM","status":"closed","priority":3,"issue_type":"task","created_at":"2025-12-24T02:51:14.432158871-05:00","updated_at":"2026-01-03T12:06:23.731969973-08:00","closed_at":"2026-01-03T12:06:23.731969973-08:00","close_reason":"Created skills.nix as single source of truth for skill names and descriptions. Updated flake.nix and Home Manager module to use it."}
{"id":"skills-8y6","title":"Define skill versioning strategy","description":"Git SHA alone is insufficient. Need tuple approach:\n\n- skill_source_rev: git SHA (if available)\n- skill_content_hash: hash of SKILL.md + scripts\n- runtime_ref: flake.lock hash or Nix store path\n\nQuestions to resolve:\n- Do Protos pin to versions (stable but maintenance) or float on latest (risky)?\n- How to handle breaking changes in skills?\n- Record in wisp trace vs proto definition?\n\nFrom consensus: both models flagged versioning instability as high severity.","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-23T19:49:30.839064445-05:00","updated_at":"2025-12-23T20:55:04.439779336-05:00","closed_at":"2025-12-23T20:55:04.439779336-05:00","close_reason":"ADRs revised with orch consensus feedback"}
{"id":"skills-9af","title":"spec-review: Add spike/research task handling","description":"Tasks like 'Investigate X' can linger without clear outcomes.\n\nAdd to REVIEW_TASKS:\n- Flag research/spike tasks\n- Require timebox and concrete outputs (decision record, prototype, risks)\n- Pattern for handling unknowns","status":"closed","priority":3,"issue_type":"task","created_at":"2025-12-15T00:23:26.887719136-08:00","updated_at":"2025-12-15T14:08:13.441095034-08:00","closed_at":"2025-12-15T14:08:13.441095034-08:00"}
@ -67,7 +68,7 @@
{"id":"skills-bcu","title":"Design doc-review skill","description":"# doc-review skill\n\nFight documentation drift with a non-interactive review process that generates patchfiles for human review.\n\n## Problem\n- No consistent documentation system across repos\n- Stale content accumulates\n- Structural inconsistencies (docs not optimized for agents)\n\n## Envisioned Workflow\n\n```bash\n# Phase 1: Generate patches (non-interactive, use spare credits, test models)\ndoc-review scan ~/proj/foo --model claude-sonnet --output /tmp/foo-patches/\n\n# Phase 2: Review patches (interactive session)\ncd ~/proj/foo\nclaude # human reviews patches, applies selectively\n```\n\n## Design Decisions Made\n\n- **Trigger**: Manual invocation (not CI). Use case includes burning extra LLM credits, testing models repeatably.\n- **Source of truth**: Style guide embedded in prompt template. Blessed defaults, overridable per-repo.\n- **Output**: Patchfiles for human review in interactive Claude session.\n- **Chunking**: Based on absolute size, not file count. Logical chunks easy for Claude to review.\n- **Scope detection**: Graph-based discovery starting from README.md or AGENTS.md, not glob-all-markdown.\n\n## Open Design Work\n\n### Agent-Friendly Doc Conventions (needs brainstorming)\nWhat makes docs agent-readable?\n- Explicit context (no \"as mentioned above\")\n- Clear section headers for navigation\n- Self-contained sections\n- Consistent terminology\n- Front-loaded summaries\n- ???\n\n### Prompt Content\nFull design round needed on:\n- What conventions to enforce\n- How to express them in prompt\n- Examples of \"good\" vs \"bad\"\n\n### Graph-Based Discovery\nHow does traversal work?\n- Parse links from README/AGENTS.md?\n- Follow relative markdown links?\n- Depth limit?\n\n## Skill Structure (tentative)\n```\nskills/doc-review/\n├── prompt.md # Core review instructions + style guide\n├── scan.sh # Orchestrates: find docs → invoke claude → emit patches\n└── README.md\n```\n\n## Out of Scope (for now)\n- Cross-repo standardization (broader than skills repo)\n- CI integration\n- Auto-apply without human review","status":"closed","priority":2,"issue_type":"feature","created_at":"2025-12-04T14:01:43.305653729-08:00","updated_at":"2025-12-04T16:44:03.468118288-08:00","closed_at":"2025-12-04T16:44:03.468118288-08:00","dependencies":[{"issue_id":"skills-bcu","depends_on_id":"skills-1ig","type":"blocks","created_at":"2025-12-04T14:02:17.144414636-08:00","created_by":"daemon","metadata":"{}"},{"issue_id":"skills-bcu","depends_on_id":"skills-53k","type":"blocks","created_at":"2025-12-04T14:02:17.164968463-08:00","created_by":"daemon","metadata":"{}"}]}
{"id":"skills-be3","title":"Define trace security and redaction policy","description":"Wisps will leak secrets without explicit policy.\n\nRequired:\n- Default-deny for env vars (allowlist: PROJECT, USER, etc.)\n- Redaction rules for sensitive fields\n- No file contents by default\n- Classification field: internal|secret|public\n\nImplementation:\n- redact: [\"env.AWS_SECRET_ACCESS_KEY\", \"inputs.token\"]\n- Sanitization before writing to disk\n- Block elevation if classification=secret\n\nFrom consensus: both models flagged as medium-high severity.","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-23T19:49:31.041661947-05:00","updated_at":"2025-12-23T20:55:04.446363188-05:00","closed_at":"2025-12-23T20:55:04.446363188-05:00","close_reason":"ADRs revised with orch consensus feedback"}
{"id":"skills-bko","title":"Prototype: Convert orch skill to emes-style","description":"First conversion to validate the pattern. Add .claude-plugin/plugin.json, restructure to skills/ directory, test discovery.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-01-09T10:59:24.812152648-08:00","created_by":"dan","updated_at":"2026-01-09T11:03:44.226707002-08:00","closed_at":"2026-01-09T11:03:44.226707002-08:00","close_reason":"Converted orch to emes-style: added .claude-plugin/plugin.json, skills/orch.md, documented pattern in docs/emes-conversion-guide.md","dependencies":[{"issue_id":"skills-bko","depends_on_id":"skills-6x1","type":"blocks","created_at":"2026-01-09T10:59:33.182232479-08:00","created_by":"dan"}]}
{"id":"skills-bo8","title":"Gemini skills access: ReadFile path restrictions block .claude/skills/","description":"Gemini agent couldn't read skill files from .claude/skills/orch/SKILL.md due to path restrictions. ReadFile tool restricts paths to workspace directories, so .claude/skills/ (symlinked from home-manager) is blocked. Agent had to fall back to shell cat command. Breaks skills portability across agents. Potential fixes: copy skills into repo, configure allowed paths, use MCP, or document workaround.","status":"open","priority":3,"issue_type":"bug","created_at":"2026-01-09T10:58:04.037329419-08:00","created_by":"dan","updated_at":"2026-01-09T10:58:17.108865761-08:00"}
{"id":"skills-bo8","title":"Gemini skills access: ReadFile path restrictions block .claude/skills/","description":"Gemini agent couldn't read skill files from .claude/skills/orch/SKILL.md due to path restrictions. ReadFile tool restricts paths to workspace directories, so .claude/skills/ (symlinked from home-manager) is blocked. Agent had to fall back to shell cat command. Breaks skills portability across agents. Potential fixes: copy skills into repo, configure allowed paths, use MCP, or document workaround.","status":"closed","priority":3,"issue_type":"bug","created_at":"2026-01-09T10:58:04.037329419-08:00","created_by":"dan","updated_at":"2026-01-09T19:35:28.068433744-08:00","closed_at":"2026-01-09T19:35:28.068433744-08:00","close_reason":"Fix found: Gemini includeDirectories setting"}
{"id":"skills-bvz","title":"spec-review: Add Definition of Ready checklists for each phase","description":"'Ready for /speckit.plan' and similar are underspecified.\n\nAdd concrete checklists:\n- Spec ready for planning: problem statement, goals, constraints, acceptance criteria, etc.\n- Plan ready for tasks: milestones, risks, dependencies, test strategy, etc.\n- Tasks ready for bd: each task has acceptance criteria, dependencies explicit, etc.","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-15T00:23:24.877531852-08:00","updated_at":"2025-12-15T14:05:26.880419097-08:00","closed_at":"2025-12-15T14:05:26.880419097-08:00"}
{"id":"skills-bww","title":"Benchmark AT-SPI overhead and coverage","description":"## Goal\nMeasure AT-SPI's runtime overhead and coverage across apps.\n\n## Prerequisites\n- Enable `services.gnome.at-spi2-core.enable = true` in NixOS\n- Set `QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1` for Qt apps\n- Rebuild and re-login\n\n## Overhead benchmarks\n1. **Startup time**: App launch with/without AT-SPI\n2. **Memory**: RSS delta with AT-SPI enabled\n3. **CPU**: Idle CPU with AT-SPI bus running\n4. **UI latency**: Input-to-paint latency (if measurable)\n\n## Coverage audit\nFor each app, document:\n- Does it expose accessibility tree?\n- How complete is the tree? (all elements vs partial)\n- Are coordinates accurate?\n- Are element types/roles correct?\n\n### Apps to test\n- [ ] Firefox\n- [ ] Ghostty terminal\n- [ ] Nautilus/file manager\n- [ ] VS Code / Electron app\n- [ ] A Qt app (if any installed)\n\n## Query benchmarks\n- Time to enumerate all elements in a window\n- Time to find element by role/name\n- Memory overhead of pyatspi queries\n\n## Depends on\n- skills-pdg (Enable AT-SPI for UI tree access)","status":"open","priority":2,"issue_type":"task","created_at":"2025-12-17T14:13:21.599259773-08:00","updated_at":"2025-12-17T14:13:21.599259773-08:00","dependencies":[{"issue_id":"skills-bww","depends_on_id":"skills-pdg","type":"blocks","created_at":"2025-12-17T14:13:41.633210539-08:00","created_by":"daemon","metadata":"{}"}]}
{"id":"skills-cc0","title":"spec-review: Add anti-hallucination constraints to prompts","description":"Models may paraphrase and present as quotes, or invent requirements/risks not in the doc.\n\nAdd:\n- 'Quotes must be verbatim'\n- 'Do not assume technologies/constraints not stated'\n- 'If missing info, list as open questions rather than speculating'","status":"closed","priority":3,"issue_type":"task","created_at":"2025-12-15T00:23:26.045478292-08:00","updated_at":"2025-12-15T14:07:19.556888057-08:00","closed_at":"2025-12-15T14:07:19.556888057-08:00"}
@ -99,7 +100,7 @@
{"id":"skills-gq9","title":"Define structured skill reference schema","description":"Replace simple skill: string with structured object.\n\nCurrent (too weak):\n skill: worklog\n\nProposed:\n skill:\n id: worklog\n ref: \"git+file://...#worklog@abc123\"\n inputs:\n session: \"{{session}}\"\n expects:\n files: [\"docs/worklogs/{{session}}.org\"]\n\nFrom orch consensus: both GPT and Gemini flagged this as critical gap.\nNo mechanism to pass args from molecule to skill.","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-23T19:49:30.529899123-05:00","updated_at":"2025-12-28T22:46:28.371352259-05:00","closed_at":"2025-12-28T22:46:28.371352259-05:00","close_reason":"Deferred: structured schema was for molecule→skill integration. Current approach (agent reads SKILL.md directly) works well. Skills as entrypoints are simpler than protos. Revisit if programmatic workflows become active.","dependencies":[{"issue_id":"skills-gq9","depends_on_id":"skills-oes","type":"blocks","created_at":"2025-12-23T19:50:10.337111856-05:00","created_by":"daemon"},{"issue_id":"skills-gq9","depends_on_id":"skills-8y6","type":"blocks","created_at":"2025-12-23T19:50:10.388301727-05:00","created_by":"daemon"}]}
{"id":"skills-gvj","title":"Orch-in-the-Middle: LSP proxy for multi-model refactors","description":"Write an LSP proxy (Go/Rust) that:\n- Intercepts rename/code-action requests from editor\n- Sends to Orch for multi-model proposals\n- Validates proposals against real headless LSP\n- Returns winning WorkspaceEdit to editor\n\nGet consensus refactoring inside VS Code/Neovim by configuring LSP server path in home-manager.","status":"closed","priority":4,"issue_type":"feature","created_at":"2025-12-24T02:29:56.623189042-05:00","updated_at":"2025-12-29T14:37:35.360129462-05:00","closed_at":"2025-12-29T14:37:35.360129462-05:00","close_reason":"Parked: waiting on gastown (Steve Yegge's orchestration layer for beads). Revisit when gastown lands."}
{"id":"skills-h9f","title":"spec-review: Balance negativity bias in prompts","description":"'Be critical' and 'devil's advocate' can bias toward over-flagging without acknowledging what's good.\n\nAdd:\n- 'List top 3 strongest parts of the document'\n- 'Call out where document is sufficiently clear/testable'\n- Categorize :against concerns as confirmed/plausible/rejected","status":"closed","priority":3,"issue_type":"task","created_at":"2025-12-15T00:23:26.418087998-08:00","updated_at":"2025-12-15T14:07:39.520818417-08:00","closed_at":"2025-12-15T14:07:39.520818417-08:00"}
{"id":"skills-hf1","title":"Cross-agent skill portability and quality gates","description":"Design and implement patterns for skills that work across multiple AI agents (Claude, Gemini, OpenCode).\n\n## Problem Statement\n\nWe want skills and quality enforcement to work regardless of which agent is:\n- The primary orchestrator\n- The worker agent\n- The reviewer agent\n\nCurrent blockers:\n- Claude Code hooks (Stop, etc.) don't exist in other agents\n- Path restrictions differ (Gemini can't read ~/.claude/skills/)\n- Subagent spawning differs across agents\n- alice/idle quality gate is Claude-specific\n\n## Goals\n\n1. **Portable skills** - Same skill works in Claude, Gemini, OpenCode\n2. **Portable quality gates** - Adversarial review pattern across agents\n3. **Flexible orchestration** - Any agent can orchestrate, any can be worker/reviewer\n\n## Key Research Areas\n\n- Dual-publish pattern (done: ADR-005)\n- Cross-agent quality gate mechanisms\n- State management (jwz vs beads vs other)\n- Protocol vs mechanical enforcement trade-offs\n- Orchestrator pattern design\n\n## Related Work\n\n- emes ecosystem (alice, jwz, tissue)\n- Our dual-publish implementation\n- orch multi-model consensus","status":"open","priority":2,"issue_type":"epic","created_at":"2026-01-09T17:13:48.116438862-08:00","created_by":"dan","updated_at":"2026-01-09T17:13:54.006968189-08:00","dependencies":[{"issue_id":"skills-hf1","depends_on_id":"skills-3gk","type":"blocks","created_at":"2026-01-09T17:14:26.901205948-08:00","created_by":"dan"},{"issue_id":"skills-hf1","depends_on_id":"skills-fqu","type":"blocks","created_at":"2026-01-09T17:14:26.940496671-08:00","created_by":"dan"},{"issue_id":"skills-hf1","depends_on_id":"skills-3ja","type":"blocks","created_at":"2026-01-09T17:14:26.97832902-08:00","created_by":"dan"},{"issue_id":"skills-hf1","depends_on_id":"skills-mjf","type":"blocks","created_at":"2026-01-09T17:14:27.011077849-08:00","created_by":"dan"},{"issue_id":"skills-hf1","depends_on_id":"skills-6fu","type":"blocks","created_at":"2026-01-09T17:14:27.045750539-08:00","created_by":"dan"},{"issue_id":"skills-hf1","depends_on_id":"skills-bo8","type":"blocks","created_at":"2026-01-09T17:14:27.150392041-08:00","created_by":"dan"},{"issue_id":"skills-hf1","depends_on_id":"skills-5kv","type":"blocks","created_at":"2026-01-09T17:14:27.192813254-08:00","created_by":"dan"},{"issue_id":"skills-hf1","depends_on_id":"skills-ut4","type":"blocks","created_at":"2026-01-09T17:32:23.828114543-08:00","created_by":"dan"},{"issue_id":"skills-hf1","depends_on_id":"skills-thk","type":"blocks","created_at":"2026-01-09T19:01:50.07496376-08:00","created_by":"dan"},{"issue_id":"skills-hf1","depends_on_id":"skills-tta","type":"blocks","created_at":"2026-01-09T19:01:50.103539768-08:00","created_by":"dan"},{"issue_id":"skills-hf1","depends_on_id":"skills-0tk","type":"blocks","created_at":"2026-01-09T19:01:50.132254456-08:00","created_by":"dan"},{"issue_id":"skills-hf1","depends_on_id":"skills-0u9","type":"blocks","created_at":"2026-01-09T19:33:03.317485233-08:00","created_by":"dan"},{"issue_id":"skills-hf1","depends_on_id":"skills-4fe","type":"blocks","created_at":"2026-01-09T19:33:03.359026048-08:00","created_by":"dan"},{"issue_id":"skills-hf1","depends_on_id":"skills-nto","type":"blocks","created_at":"2026-01-09T19:33:03.385366262-08:00","created_by":"dan"},{"issue_id":"skills-hf1","depends_on_id":"skills-8nl","type":"blocks","created_at":"2026-01-09T19:33:03.420512171-08:00","created_by":"dan"}]}
{"id":"skills-hf1","title":"Cross-agent skill portability and quality gates","description":"Design and implement cross-agent skill portability and quality gates.\n\n## Problem Statement\n\nSkills and quality enforcement must work regardless of which agent is orchestrator, worker, or reviewer. Current agents (Claude, Gemini, OpenCode, Codex) have different capabilities.\n\n## Abstract Architecture\n\n### Layer 1: Message Passing\n**Purpose:** Async agent coordination, session handoffs, status updates\n\n| Requirement | Description |\n|-------------|-------------|\n| Append-only | No overwrites, git-mergeable |\n| Agent-attributed | Know which agent posted |\n| Topic-based | Namespaced conversations |\n| Async | Agents don't block each other |\n\n*Possible implementations:* jwz, beads extensions, simple JSONL files\n\n### Layer 2: Memory \n**Purpose:** Persistent work items, dependencies, review state\n\n| Requirement | Description |\n|-------------|-------------|\n| Cross-session | Survives compaction, restarts |\n| Dependency tracking | Issue X blocks issue Y |\n| Queryable | Find by status, type, assignee |\n| Git-native | Lives in repo, versioned |\n\n*Possible implementations:* beads, tissue, structured markdown\n\n### Layer 3: Enforcement\n**Purpose:** Quality gates that block completion until approved\n\n| Requirement | Description |\n|-------------|-------------|\n| Mechanical where possible | Hooks for Claude/Gemini |\n| Protocol fallback | Orchestrator-enforced for others |\n| Circuit breakers | Prevent infinite loops |\n| Reviewable | Human can inspect decisions |\n\n*Possible implementations:* Stop hooks, orchestrator gates, wrapper scripts\n\n## Goals\n\n1. **Portable skills** - Same SKILL.md works in any agent\n2. **Portable quality gates** - Adversarial review across agents\n3. **Flexible orchestration** - Any agent can play any role\n4. **Implementation-agnostic** - Swap tools without changing patterns\n\n## Completed Work\n- ADR-005: Dual-publish architecture\n- Agent capability matrix\n- Web research on patterns\n- orch integration for multi-model\n\n## Key Decisions Pending\n- Message passing: jwz vs beads vs simple files\n- Enforcement: Hook-first vs orchestrator-first\n- Reviewer: Dedicated skill vs orch consensus","status":"open","priority":2,"issue_type":"epic","created_at":"2026-01-09T17:13:48.116438862-08:00","created_by":"dan","updated_at":"2026-01-09T19:34:02.490045488-08:00","dependencies":[{"issue_id":"skills-hf1","depends_on_id":"skills-3gk","type":"blocks","created_at":"2026-01-09T17:14:26.901205948-08:00","created_by":"dan"},{"issue_id":"skills-hf1","depends_on_id":"skills-fqu","type":"blocks","created_at":"2026-01-09T17:14:26.940496671-08:00","created_by":"dan"},{"issue_id":"skills-hf1","depends_on_id":"skills-3ja","type":"blocks","created_at":"2026-01-09T17:14:26.97832902-08:00","created_by":"dan"},{"issue_id":"skills-hf1","depends_on_id":"skills-mjf","type":"blocks","created_at":"2026-01-09T17:14:27.011077849-08:00","created_by":"dan"},{"issue_id":"skills-hf1","depends_on_id":"skills-6fu","type":"blocks","created_at":"2026-01-09T17:14:27.045750539-08:00","created_by":"dan"},{"issue_id":"skills-hf1","depends_on_id":"skills-bo8","type":"blocks","created_at":"2026-01-09T17:14:27.150392041-08:00","created_by":"dan"},{"issue_id":"skills-hf1","depends_on_id":"skills-5kv","type":"blocks","created_at":"2026-01-09T17:14:27.192813254-08:00","created_by":"dan"},{"issue_id":"skills-hf1","depends_on_id":"skills-ut4","type":"blocks","created_at":"2026-01-09T17:32:23.828114543-08:00","created_by":"dan"},{"issue_id":"skills-hf1","depends_on_id":"skills-thk","type":"blocks","created_at":"2026-01-09T19:01:50.07496376-08:00","created_by":"dan"},{"issue_id":"skills-hf1","depends_on_id":"skills-tta","type":"blocks","created_at":"2026-01-09T19:01:50.103539768-08:00","created_by":"dan"},{"issue_id":"skills-hf1","depends_on_id":"skills-0tk","type":"blocks","created_at":"2026-01-09T19:01:50.132254456-08:00","created_by":"dan"},{"issue_id":"skills-hf1","depends_on_id":"skills-0u9","type":"blocks","created_at":"2026-01-09T19:33:03.317485233-08:00","created_by":"dan"},{"issue_id":"skills-hf1","depends_on_id":"skills-4fe","type":"blocks","created_at":"2026-01-09T19:33:03.359026048-08:00","created_by":"dan"},{"issue_id":"skills-hf1","depends_on_id":"skills-nto","type":"blocks","created_at":"2026-01-09T19:33:03.385366262-08:00","created_by":"dan"},{"issue_id":"skills-hf1","depends_on_id":"skills-8nl","type":"blocks","created_at":"2026-01-09T19:33:03.420512171-08:00","created_by":"dan"},{"issue_id":"skills-hf1","depends_on_id":"skills-8sj","type":"blocks","created_at":"2026-01-09T19:33:36.855745049-08:00","created_by":"dan"}]}
{"id":"skills-hgm","title":"Add tests for agent file update logic","description":"File: .specify/scripts/bash/update-agent-context.sh (lines 360-499)\n\nCritical logic with NO test coverage:\n- Malformed agent files (missing sections)\n- Multiple section headers on same line\n- Empty file handling\n- Timestamp update verification\n- State machine correctness\n\nRisk: HIGH - corrupts agent context files on failure\n\nFix:\n- Create test fixtures for various file states\n- Test each state transition\n- Verify idempotency\n\nSeverity: HIGH","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-24T02:51:00.793493549-05:00","updated_at":"2026-01-02T02:12:09.368531967-05:00","closed_at":"2026-01-02T02:12:09.368531967-05:00","close_reason":"33 tests added covering all major code paths. Also fixed bug where Recent Changes section was skipped when preceded by Active Technologies."}
{"id":"skills-hh2","title":"skill: rename_symbol with LSP + validation","description":"Skill that performs safe renames:\n1. Uses LSP textDocument/rename\n2. Runs formatters\n3. Checks LSP diagnostics post-rename\n4. Opens bead if errors remain\n5. Updates doc references using hover/signatureHelp\n\nInput: new name, scope. Output: clean rename or bead with issues.","status":"open","priority":3,"issue_type":"task","created_at":"2025-12-24T02:29:56.87156069-05:00","updated_at":"2025-12-24T02:29:56.87156069-05:00","dependencies":[{"issue_id":"skills-hh2","depends_on_id":"skills-gga","type":"blocks","created_at":"2025-12-24T02:30:06.583813579-05:00","created_by":"daemon"}]}
{"id":"skills-hhz","title":"Add doc-review skill","description":"Create skill for doc-review CLI tool (~/proj/doc-review). Tool lints markdown docs for AI agent consumption using Vale + LLM hybrid architecture. Needs: 1) flake.nix in doc-review project, 2) skill SKILL.md, 3) register in availableSkills","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-30T11:24:41.321478346-05:00","created_by":"dan","updated_at":"2025-12-31T00:00:30.74314365-05:00","closed_at":"2025-12-31T00:00:30.74314365-05:00","close_reason":"doc-review skill created in skills/doc-review/SKILL.md"}
@ -130,7 +131,7 @@
{"id":"skills-rex","title":"Test integration on worklog skill","description":"Use worklog skill as first real test case:\n- Create wisp for worklog execution\n- Capture execution trace\n- Test squash → digest\n- Validate trace format captures enough info for replay\n\nMigrated from dotfiles-drs.","status":"closed","priority":3,"issue_type":"task","created_at":"2025-12-23T19:21:18.75525644-05:00","updated_at":"2025-12-29T13:55:35.814174815-05:00","closed_at":"2025-12-29T13:55:35.814174815-05:00","close_reason":"Parked with ADR-001: skills-molecules integration deferred. Current simpler approach (skills as standalone) works well. Revisit when complex orchestration needed.","dependencies":[{"issue_id":"skills-rex","depends_on_id":"skills-3em","type":"blocks","created_at":"2025-12-23T19:22:00.34922734-05:00","created_by":"dan"}]}
{"id":"skills-rpf","title":"Implement playwright-visit skill for browser automation","description":"## Overview\nBrowser automation skill using Playwright to visit web pages, take screenshots, and extract content.\n\n## Key Findings (from dotfiles investigation)\n\n### Working Setup\n- Use `python312Packages.playwright` from nixpkgs (handles Node driver binary patching for NixOS)\n- Use `executable_path='/run/current-system/sw/bin/chromium'` to use system chromium\n- No `playwright install` needed - no browser binary downloads\n\n### Profile Behavior\n- Fresh/blank profile every launch by default\n- No cookies, history, or logins from user's browser\n- Can persist state with `storage_state` parameter if needed\n\n### Example Code\n```python\nfrom playwright.sync_api import sync_playwright\n\nwith sync_playwright() as p:\n browser = p.chromium.launch(\n executable_path='/run/current-system/sw/bin/chromium',\n headless=True\n )\n page = browser.new_page()\n page.goto('https://example.com')\n print(page.title())\n browser.close()\n```\n\n### Why Not uv/pip?\n- Playwright pip package bundles a Node.js driver binary\n- NixOS can't run dynamically linked executables without patching\n- nixpkgs playwright handles this properly\n\n## Implementation Plan\n1. Create `skills/playwright-visit/` directory\n2. Add flake.nix with devShell providing playwright\n3. Create CLI script with subcommands:\n - `screenshot \u003curl\u003e \u003coutput.png\u003e` - capture page\n - `text \u003curl\u003e` - extract text content \n - `html \u003curl\u003e` - get rendered HTML\n - `pdf \u003curl\u003e \u003coutput.pdf\u003e` - save as PDF\n4. Create skill definition for Claude Code integration\n5. Document usage in skill README\n\n## Dependencies\n- nixpkgs python312Packages.playwright\n- System chromium (already in dotfiles)\n\n## Related\n- dotfiles issue dotfiles-m09 (playwright skill request)","status":"closed","priority":2,"issue_type":"feature","created_at":"2025-12-16T16:02:28.577381007-08:00","updated_at":"2025-12-29T00:09:50.681141882-05:00","closed_at":"2025-12-29T00:09:50.681141882-05:00","close_reason":"Implemented: SKILL.md, visit.py CLI (screenshot/text/html/pdf), flake.nix devShell, README. Network down so couldn't test devShell build, but code complete."}
{"id":"skills-s92","title":"Add tests for config injection (deploy-skill.sh)","description":"File: bin/deploy-skill.sh (lines 112-137)\n\nCritical logic with NO test coverage:\n- Idempotency (running twice should be safe)\n- Correct brace matching in Nix\n- Syntax validity of injected config\n- Rollback on failure\n\nRisk: MEDIUM-HIGH - can break dotfiles Nix config\n\nFix:\n- Test idempotent injection\n- Validate Nix syntax after injection\n- Test with malformed input\n\nSeverity: MEDIUM","status":"closed","priority":3,"issue_type":"task","created_at":"2025-12-24T02:51:01.314513824-05:00","updated_at":"2026-01-06T16:29:18.728097676-08:00","closed_at":"2026-01-06T16:29:18.728097676-08:00","close_reason":"21 tests added covering idempotency, brace preservation, inject_home_file wrapper, edge cases"}
{"id":"skills-thk","title":"Design: Hybrid hook + gate architecture","description":"Design enforcement that uses hooks where available, orchestrator gates elsewhere.\n\n## Hook-Capable Agents (Claude, Gemini)\n- Stop hook checks beads for review status\n- Mechanical enforcement - agent can't bypass\n\n## Non-Hook Agents (OpenCode, Codex) \n- Orchestrator pattern enforces gate\n- Orchestrator checks beads before declaring done\n- Worker can't bypass because doesn't control session\n\n## Shared Components\n- beads: persistent state (issues, review status)\n- jwz: transient state (session messages, async handoffs)\n- review-gate CLI: checks state, returns exit code\n\n## Deliverable\nArchitecture doc showing:\n1. Hook configuration for Claude/Gemini\n2. Orchestrator flow for OpenCode/Codex\n3. State schema in beads\n4. review-gate CLI design","status":"open","priority":2,"issue_type":"task","created_at":"2026-01-09T19:01:24.270855877-08:00","created_by":"dan","updated_at":"2026-01-09T19:01:24.270855877-08:00"}
{"id":"skills-thk","title":"Design: Hybrid hook + gate architecture","description":"Design enforcement that uses hooks where available, orchestrator gates elsewhere.\n\n## Hook-Capable Agents (Claude, Gemini)\n- Stop hook checks beads for review status\n- Mechanical enforcement - agent can't bypass\n\n## Non-Hook Agents (OpenCode, Codex) \n- Orchestrator pattern enforces gate\n- Orchestrator checks beads before declaring done\n- Worker can't bypass because doesn't control session\n\n## Shared Components\n- beads: persistent state (issues, review status)\n- jwz: transient state (session messages, async handoffs)\n- review-gate CLI: checks state, returns exit code\n\n## Deliverable\nArchitecture doc showing:\n1. Hook configuration for Claude/Gemini\n2. Orchestrator flow for OpenCode/Codex\n3. State schema in beads\n4. review-gate CLI design","status":"closed","priority":2,"issue_type":"task","created_at":"2026-01-09T19:01:24.270855877-08:00","created_by":"dan","updated_at":"2026-01-09T19:33:36.705975116-08:00","closed_at":"2026-01-09T19:33:36.705975116-08:00","close_reason":"Consolidated into skills-8sj"}
{"id":"skills-tta","title":"Design: Circuit breaker patterns","description":"Design circuit breakers to prevent agent infinite loops.\n\n## Patterns to Implement\n\n### Semantic Drift Detection\n- Embed last N agent thoughts\n- If \u003e95% similar, inject \"try different approach\"\n- Use cheap embedding model\n\n### Three-Strike Tool Rule \n- Track tool call signatures (tool + args + error)\n- 3 identical failures → force strategy shift\n- Implement in PostToolUse hook\n\n### Budget-Based Interrupts\n- Allocate token budget per sub-task\n- Pause if \u003e50% budget used with \u003c30% progress\n- Request plan refinement\n\n### Time-Based Breaker\n- Timeout per task type\n- Escalate to review if exceeded\n\n## Implementation Options\n- Hook-based (Claude/Gemini)\n- Wrapper-based (all agents)\n- Orchestrator-enforced (all agents)\n\n## Deliverable\n- Circuit breaker design doc\n- Prototype implementation for one pattern","status":"open","priority":2,"issue_type":"task","created_at":"2026-01-09T19:01:44.536499408-08:00","created_by":"dan","updated_at":"2026-01-09T19:01:44.536499408-08:00"}
{"id":"skills-ty7","title":"Define trace levels (audit vs debug)","description":"Two trace levels to manage noise vs utility:\n\n1. Audit trace (minimal, safe, always on):\n - skill id/ref, start/end\n - high-level checkpoints\n - artifact hashes/paths\n - exit status\n\n2. Debug trace (opt-in, verbose):\n - tool calls with args\n - stdout/stderr snippets\n - expanded inputs\n - timing details\n\nConsider OpenTelemetry span model as reference.\nGPT proposed this; Gemini focused on rotation/caps instead.","status":"closed","priority":3,"issue_type":"task","created_at":"2025-12-23T19:49:48.514684945-05:00","updated_at":"2025-12-29T13:55:35.838961236-05:00","closed_at":"2025-12-29T13:55:35.838961236-05:00","close_reason":"Parked with ADR-001: skills-molecules integration deferred. Current simpler approach (skills as standalone) works well. Revisit when complex orchestration needed."}
{"id":"skills-u3d","title":"Define skill trigger conditions","description":"How does an agent know WHEN to apply a skill/checklist?\n\nOptions:\n- frontmatter triggers: field with patterns\n- File-based detection\n- Agent judgment from description\n- Beads hooks on state transitions\n- LLM-based pattern detection","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-23T17:59:09.69468767-05:00","updated_at":"2025-12-28T22:25:38.579989006-05:00","closed_at":"2025-12-28T22:25:38.579989006-05:00","close_reason":"Resolved: agent judgment from description is the standard. Good descriptions + 'When to Use' sections are sufficient. No new trigger mechanism needed - would add complexity without clear benefit."}

View file

@ -138,7 +138,11 @@ Limited: notification hooks, approval hooks, event loop lifecycle
- Full filesystem access
- **Known issue:** ReadFile restricts to workspace directories
- Symlinked paths (like ~/.claude/skills/) may be blocked
- Workaround: use shell `cat` command
- **Fix:** Add to `~/.gemini/settings.json`:
```json
{ "context": { "includeDirectories": ["~/.claude/skills"] } }
```
- Or use `gemini --include-directories ~/.claude/skills`
#### OpenCode
- Configurable permissions per operation