bd sync: 2026-01-10 15:41:05
This commit is contained in:
dan
parent
0fcfbe0624
commit
713a627185
|
|
@ -3,21 +3,25 @@
|
|||
{"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":"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-0y9","title":"Design: Structured task specs (requirements/design/tasks)","description":"Adopt spec-driven development pattern from Kiro/Tessl/GitHub Spec Kit. Each task should have: requirements.md (what), design.md (how), tasks.md (decomposed steps). Agents work from specs not vague prompts. Specs are versioned; agents echo which version they used. Prevents state divergence and 'different reality' footgun.","status":"open","priority":2,"issue_type":"task","created_at":"2026-01-10T15:40:59.99198595-08:00","created_by":"dan","updated_at":"2026-01-10T15:40:59.99198595-08:00","dependencies":[{"issue_id":"skills-0y9","depends_on_id":"skills-s6y","type":"blocks","created_at":"2026-01-10T15:41:00.005934153-08:00","created_by":"dan"}]}
|
||||
{"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-1jc","title":"Design: Stuck agent detection (Rubber Duck)","description":"Detect non-progress and force clarification.\n\n## Pattern (from GPT/Gemini brainstorm)\nTrack:\n- repeated tool calls (same command 3x)\n- identical errors\n- no diff delta\n- no new hypotheses\n\nWhen triggered, force protocol:\n1. Write down 3 hypotheses\n2. Run one discriminating experiment per hypothesis\n3. If no new info → escalate\n\n## Rubber Duck variant\nOn stuck: force agent to explain problem in 200 tokens to dumber model.\nIf can't explain coherently → escalate to human.\nCompression reveals the flaw.\n\n## Abstraction Elevator variant\nStuck on syntax → force to pseudocode\nStuck on logic → force to explain with analogies\n\n## Implementation\n- worker stuck X - detect non-progress\n- Check .worker-state/X.log for repeated patterns\n- Inject 'rubber duck' prompt if stuck\n- Circuit breaker after N attempts","status":"open","priority":2,"issue_type":"task","created_at":"2026-01-10T12:14:51.130472999-08:00","created_by":"dan","updated_at":"2026-01-10T12:14:51.130472999-08:00","dependencies":[{"issue_id":"skills-1jc","depends_on_id":"skills-s6y","type":"blocks","created_at":"2026-01-10T12:15:10.15494718-08:00","created_by":"dan"}]}
|
||||
{"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"}
|
||||
{"id":"skills-1n3","title":"Set up agent skills for Gemini CLI","description":"The AI agent skills (worklog, web-search, etc.) configured in .skills are not currently working when using the Gemini CLI. \\n\\nObserved behavior:\\n- 'worklog' command not found even after 'direnv reload'.\\n- .envrc sources ~/proj/skills/bin/use-skills.sh, but skills are not accessible in the Gemini agent session.\\n\\nNeed to:\\n1. Investigate how Gemini CLI loads its environment compared to Claude Code.\\n2. Update 'use-skills.sh' or direnv configuration to support Gemini CLI.\\n3. Ensure skill symlinks/binaries are correctly in the PATH for Gemini.","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-22T17:39:28.106296919-05:00","updated_at":"2025-12-28T22:28:49.781533243-05:00","closed_at":"2025-12-28T22:28:49.781533243-05:00","close_reason":"No MCP/extensions. Gemini CLI lacks native skill support (feature request #11506 pending). Current workaround: GEMINI.md references skill paths for manual reading. Revisit when native support lands."}
|
||||
{"id":"skills-1qz","title":"Design: Token and cost budgets per agent","description":"Prevent token blowup footgun. Implement: hard budgets per agent and per run, limit context sizes, separate heavy/light agents, queueing with backpressure, retry with idempotency tokens. Plan-and-Execute pattern: expensive model plans, cheap models execute (90% cost reduction). From research synthesis.","status":"open","priority":3,"issue_type":"task","created_at":"2026-01-10T15:41:00.383262566-08:00","created_by":"dan","updated_at":"2026-01-10T15:41:00.383262566-08:00","dependencies":[{"issue_id":"skills-1qz","depends_on_id":"skills-s6y","type":"blocks","created_at":"2026-01-10T15:41:00.383903314-08:00","created_by":"dan"}]}
|
||||
{"id":"skills-20s","title":"Compare BOUNDARIES.md with upstream","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-03T20:15:53.585115099-08:00","updated_at":"2025-12-03T20:19:28.442646801-08:00","closed_at":"2025-12-03T20:19:28.442646801-08:00","dependencies":[{"issue_id":"skills-20s","depends_on_id":"skills-ebh","type":"discovered-from","created_at":"2025-12-03T20:15:53.586442134-08:00","created_by":"daemon","metadata":"{}"}]}
|
||||
{"id":"skills-25l","title":"Create orch skill for multi-model consensus","description":"Build a skill that exposes orch CLI capabilities to agents for querying multiple AI models","status":"closed","priority":2,"issue_type":"feature","created_at":"2025-11-30T15:43:49.209528963-08:00","updated_at":"2025-11-30T15:47:36.608887453-08:00","closed_at":"2025-11-30T15:47:36.608887453-08:00"}
|
||||
{"id":"skills-2hp","title":"Define agent autonomy policy for skills","description":"Disagreement in consensus:\n\nGPT: Stricter determinism to prevent 'agent drift'\nGemini: skill: should be a hint, agent can deviate if skill fails\n\nOptions:\n1. Constraint (must use skill, fail if broken)\n2. Heuristic (should use, can justify deviation)\n3. Configurable per-proto or per-step\n\nUX consideration: agents stuck in loops trying broken skills.\n\nNeeds decision before widespread adoption.","status":"closed","priority":4,"issue_type":"task","created_at":"2025-12-23T19:49:59.73500059-05:00","updated_at":"2025-12-29T14:37:35.335994418-05:00","closed_at":"2025-12-29T14:37:35.335994418-05:00","close_reason":"Parked: waiting on gastown (Steve Yegge's orchestration layer for beads). Revisit when gastown lands."}
|
||||
{"id":"skills-2k0","title":"Reframe elevation as scaffolding","description":"Elevation pipeline is over-optimistic. Auto-generation will produce garbage.\n\nReframe:\n- Rename to 'Pattern Extraction' or 'Skill Drafting'\n- Output is skeleton/scaffold, not complete skill\n- Require N\u003e=3 similar executions before suggesting\n- Generate promotion checklist:\n - Preconditions\n - Inputs/outputs contract\n - Failure modes observed\n - Determinism score\n- Generate tests as part of elevation\n\nHuman-in-the-loop is mandatory, not optional.\n\nFrom consensus: both models flagged as medium severity.","status":"closed","priority":3,"issue_type":"task","created_at":"2025-12-23T19:49:48.373417035-05:00","updated_at":"2025-12-29T13:55:35.820906687-05:00","closed_at":"2025-12-29T13:55:35.820906687-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-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-31y","title":"Design: Review funnel with arbiter agent","description":"Solve review bottleneck footgun (10 agents = 10 PRs to reconcile). Add arbiter/synthesis step: workers → arbiter agent (dedupes, resolves conflicts) → single synthesized PR → human review. Pre-review by lint/style agents so humans see substantive deltas only. From HN discussions on parallel agents.","status":"open","priority":2,"issue_type":"task","created_at":"2026-01-10T15:41:00.232426243-08:00","created_by":"dan","updated_at":"2026-01-10T15:41:00.232426243-08:00","dependencies":[{"issue_id":"skills-31y","depends_on_id":"skills-s6y","type":"blocks","created_at":"2026-01-10T15:41:00.233443613-08:00","created_by":"dan"}]}
|
||||
{"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":"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-4a2","title":"Design: Role boundaries with tool constraints","description":"Prevent role collapse footgun (planner writing code, tester refactoring). Implement tool-level constraints per agent type: some agents read-only, some propose patches only, only orchestrator commits. Reject outputs that violate role boundaries. From orch consensus and HN practitioner feedback.","status":"open","priority":2,"issue_type":"task","created_at":"2026-01-10T15:41:00.12208959-08:00","created_by":"dan","updated_at":"2026-01-10T15:41:00.12208959-08:00","dependencies":[{"issue_id":"skills-4a2","depends_on_id":"skills-s6y","type":"blocks","created_at":"2026-01-10T15:41:00.123172375-08:00","created_by":"dan"}]}
|
||||
{"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-4oj","title":"Design: Worker state machine (ASSIGNED→WORKING→REVIEW→MERGED)","description":"Consensus gap: 'Done' state is ambiguous. Need explicit state machine. States: ASSIGNED → WORKING → REVIEW_REQUESTED → APPROVED → MERGED. Each state transition via file update. Clear handoff points between worker/reviewer/orchestrator.","design":"docs/design/worker-state-machine.md","notes":"Design complete. 8 states: IDLE → ASSIGNED → WORKING → IN_REVIEW → APPROVED → COMPLETED, plus STALE and FAILED. File-based coordination using atomic rename pattern. Stale detection via heartbeat + PID checks. Integrates with review-gate, message passing, and branch isolation.","status":"open","priority":2,"issue_type":"task","created_at":"2026-01-10T13:55:23.733457598-08:00","created_by":"dan","updated_at":"2026-01-10T14:01:19.39170134-08:00","dependencies":[{"issue_id":"skills-4oj","depends_on_id":"skills-s6y","type":"blocks","created_at":"2026-01-10T13:55:23.743143692-08:00","created_by":"dan"}]}
|
||||
{"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"}
|
||||
|
|
@ -25,6 +29,7 @@
|
|||
{"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."}
|
||||
{"id":"skills-53k","title":"Design graph-based doc discovery","description":"How does doc-review find and traverse documentation?\n\nApproach: Start from README.md or AGENTS.md, graph out from there.\n\nDesign questions:\n- Parse markdown links to find related docs?\n- Follow only relative links or also section references?\n- How to handle circular references?\n- Depth limit or exhaustive traversal?\n- What about orphan docs not linked from root?\n- How to represent the graph for chunking decisions?\n\nConsiderations:\n- Large repos may have hundreds of markdown files\n- Not all .md files are \"documentation\" (changelogs, templates, etc.)\n- Some docs are generated and shouldn't be patched\n\nDeliverable: Algorithm/pseudocode for doc discovery + chunking strategy.","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-04T14:02:13.316843518-08:00","updated_at":"2025-12-04T16:43:58.277061015-08:00","closed_at":"2025-12-04T16:43:58.277061015-08:00"}
|
||||
{"id":"skills-5hb","title":"spec-review: Add Prerequisites section documenting dependencies","description":"SKILL.md and process docs assume orch is installed, prompt files exist, models are available, but none of this is documented.\n\nAdd:\n- orch install instructions/link\n- Required env vars and model availability\n- Prompt file locations\n- Expected repo structure (specs/ convention)\n- Troubleshooting section for common failures","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-15T00:23:23.030537501-08:00","updated_at":"2025-12-15T01:12:36.457092612-08:00","closed_at":"2025-12-15T01:12:36.457092612-08:00"}
|
||||
{"id":"skills-5ji","title":"Design: Ephemeral namespaced environments","description":"Solve shared state pollution footgun. Each worker branch gets: namespaced DB (schema prefix or separate DB), isolated Redis namespace, separate queues, namespaced feature flags. Agents never touch shared prod-like state. Idempotent migrations and fixture loaders. From HN practitioner feedback on database isolation.","status":"open","priority":3,"issue_type":"task","created_at":"2026-01-10T15:41:00.720141358-08:00","created_by":"dan","updated_at":"2026-01-10T15:41:00.720141358-08:00","dependencies":[{"issue_id":"skills-5ji","depends_on_id":"skills-s6y","type":"blocks","created_at":"2026-01-10T15:41:00.721467429-08:00","created_by":"dan"}]}
|
||||
{"id":"skills-5kv","title":"Document beads vs tissue split during emes testing","description":"During emes testing on ops-jrz1:\n- Local dev: beads (skills repo, dotfiles, etc.)\n- ops-jrz1: tissue (emes ecosystem testing)\n\nNeed to document:\n- Which tracker for which repos\n- How to context-switch mentally\n- Whether to bridge or keep separate\n- Exit criteria: when do we converge?","status":"closed","priority":3,"issue_type":"task","created_at":"2026-01-09T16:03:45.493255636-08:00","created_by":"dan","updated_at":"2026-01-09T19:59:37.885799343-08:00","closed_at":"2026-01-09T19:59:37.885799343-08:00","close_reason":"Superseded by abstract layer approach - memory layer abstracts beads/tissue"}
|
||||
{"id":"skills-5tq","title":"LSP diagnostic harvest → auto-create beads","description":"Periodic/nightly headless LSP scan that:\n- Gathers diagnostics (unused vars, type errors, deprecations, lint warnings)\n- Groups by subsystem/module\n- Auto-creates beads with severity thresholds\n- Enables 'refactor quests' - parent bead with children per symbol\n\nRun via CI or cron, feed results back into beads automatically.","status":"open","priority":3,"issue_type":"feature","created_at":"2025-12-24T02:29:56.191762416-05:00","updated_at":"2025-12-24T02:29:56.191762416-05:00","dependencies":[{"issue_id":"skills-5tq","depends_on_id":"skills-gga","type":"blocks","created_at":"2025-12-24T02:30:06.471853411-05:00","created_by":"daemon"}]}
|
||||
{"id":"skills-5v8","title":"Replace SKILL.md with upstream version","description":"Upstream has 644 lines vs our 122. Missing: self-test questions, notes quality checks, token checkpointing, database selection, field usage table, lifecycle workflow, common patterns, troubleshooting","status":"closed","priority":1,"issue_type":"task","created_at":"2025-12-03T20:15:53.025829293-08:00","updated_at":"2025-12-03T20:16:20.470185004-08:00","closed_at":"2025-12-03T20:16:20.470185004-08:00","dependencies":[{"issue_id":"skills-5v8","depends_on_id":"skills-ebh","type":"discovered-from","created_at":"2025-12-03T20:15:53.027601712-08:00","created_by":"daemon","metadata":"{}"}]}
|
||||
|
|
@ -39,6 +44,7 @@
|
|||
{"id":"skills-7n4","title":"Design: Rollback strategy for failed workers","description":"Consensus gap: No rollback strategy. Handle: stuck workers, rejected reviews, merge conflicts. Branch archive/delete, state reset for re-assignment, evidence preservation for debugging.","status":"open","priority":3,"issue_type":"task","created_at":"2026-01-10T13:55:24.144602107-08:00","created_by":"dan","updated_at":"2026-01-10T13:55:24.144602107-08:00","dependencies":[{"issue_id":"skills-7n4","depends_on_id":"skills-s6y","type":"blocks","created_at":"2026-01-10T13:55:24.147809879-08:00","created_by":"dan"}]}
|
||||
{"id":"skills-7s0","title":"Compare STATIC_DATA.md with upstream","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-03T20:15:55.193704589-08:00","updated_at":"2025-12-03T20:19:29.659256809-08:00","closed_at":"2025-12-03T20:19:29.659256809-08:00","dependencies":[{"issue_id":"skills-7s0","depends_on_id":"skills-ebh","type":"discovered-from","created_at":"2025-12-03T20:15:55.195160705-08:00","created_by":"daemon","metadata":"{}"}]}
|
||||
{"id":"skills-7sh","title":"Set up bd-issue-tracking Claude Code skill from beads repo","description":"Install the beads Claude Code skill from https://github.com/steveyegge/beads/tree/main/examples/claude-code-skill\n\nThis skill teaches Claude how to effectively use beads for issue tracking across multi-session coding workflows. It provides strategic guidance on when/how to use beads, not just command syntax.\n\nFiles to install to ~/.claude/skills/bd-issue-tracking/:\n- SKILL.md - Core workflow patterns and decision criteria\n- BOUNDARIES.md - When to use beads vs markdown alternatives\n- CLI_REFERENCE.md - Complete command documentation\n- DEPENDENCIES.md - Relationship types and patterns\n- WORKFLOWS.md - Step-by-step procedures\n- ISSUE_CREATION.md - Quality guidelines\n- RESUMABILITY.md - Making work resumable across sessions\n- STATIC_DATA.md - Using beads as reference databases\n\nCan symlink or copy the files. Restart Claude Code after install.","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-03T17:53:43.254007992-08:00","updated_at":"2025-12-03T20:04:53.416579381-08:00","closed_at":"2025-12-03T20:04:53.416579381-08:00"}
|
||||
{"id":"skills-8ak","title":"Evaluate: Git bundle checkpoints (SkillFS pattern)","description":"SkillFS pattern: every agent sandbox is a git repo. Session ends → git bundle stored. New session → restore from bundle, continue where left off. Provides: persistence across sessions, full audit trail via git log, crash recovery. Evaluate if this fits our architecture or if worktrees are sufficient. See github.com/mupt-ai/skillfs","status":"open","priority":3,"issue_type":"task","created_at":"2026-01-10T15:41:00.52226419-08:00","created_by":"dan","updated_at":"2026-01-10T15:41:00.52226419-08:00","dependencies":[{"issue_id":"skills-8ak","depends_on_id":"skills-s6y","type":"blocks","created_at":"2026-01-10T15:41:00.523166841-08:00","created_by":"dan"}]}
|
||||
{"id":"skills-8cc","title":"Remove dead code: unused ARGS variable","description":"File: .specify/scripts/bash/create-new-feature.sh\n\nLine 8: ARGS=() declared but never used\nLine 251: export SPECIFY_FEATURE - unclear if used downstream\n\nFix:\n- Remove unused ARGS declaration\n- Verify SPECIFY_FEATURE is used or remove\n\nSeverity: LOW","status":"closed","priority":4,"issue_type":"task","created_at":"2025-12-24T02:50:59.332192076-05:00","updated_at":"2025-12-29T18:38:03.48883384-05:00","closed_at":"2025-12-29T18:38:03.48883384-05:00","close_reason":"Invalid: ARGS is used (line 58, 64). SPECIFY_FEATURE is used by common.sh for feature detection. No dead code."}
|
||||
{"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."}
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
skills-yc6
|
||||
skills-5ji
|
||||
|
|
|
|||
Loading…
Reference in a new issue