bd daemon export: 2026-01-19 14:40:56
This commit is contained in:
parent
0fdb534243
commit
6a9260c2f6
|
|
@ -72,7 +72,7 @@
|
||||||
{"id":"skills-6n4u","title":"Spike: manually test Claude in worker context","description":"Simple experiment - no harness, no automation.\n\n## Goal\nLearn what happens when Claude tries to complete a task using the worker system.\n\n## Steps\n1. Set up a simple fixture (python-math-lib exists)\n2. worker spawn test-spike\n3. cd into worktree\n4. Invoke Claude with task: \"Add a factorial function to src/math_utils.py\"\n5. Include system context about worker commands (start, done, heartbeat)\n6. Watch what happens\n\n## Observe\n- Does Claude understand the worker flow?\n- Does it run worker start / worker done correctly?\n- Does it complete the task?\n- How many turns? What goes wrong?\n- What prompting helps?\n\n## Output\nNotes on what worked, what didn't, what's needed.\nInform whether we need the full harness or something simpler.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-01-11T16:38:49.022489161-08:00","created_by":"dan","updated_at":"2026-01-11T19:15:47.037731412-08:00","closed_at":"2026-01-11T19:15:47.037731412-08:00","close_reason":"Spike completed successfully.\n\nObservations:\n1. Worker flow works: spawn → start → work → done → approve → merge\n2. Found and fixed bug: relative worktree paths (skills-5ry7)\n3. Claude (me) completed the task using worker CLI without special prompting\n4. ~7 tool calls to complete simple task\n5. Test script needed sqlite3 in PATH - added check\n\nThe worker system is functional for basic agent tasks."}
|
{"id":"skills-6n4u","title":"Spike: manually test Claude in worker context","description":"Simple experiment - no harness, no automation.\n\n## Goal\nLearn what happens when Claude tries to complete a task using the worker system.\n\n## Steps\n1. Set up a simple fixture (python-math-lib exists)\n2. worker spawn test-spike\n3. cd into worktree\n4. Invoke Claude with task: \"Add a factorial function to src/math_utils.py\"\n5. Include system context about worker commands (start, done, heartbeat)\n6. Watch what happens\n\n## Observe\n- Does Claude understand the worker flow?\n- Does it run worker start / worker done correctly?\n- Does it complete the task?\n- How many turns? What goes wrong?\n- What prompting helps?\n\n## Output\nNotes on what worked, what didn't, what's needed.\nInform whether we need the full harness or something simpler.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-01-11T16:38:49.022489161-08:00","created_by":"dan","updated_at":"2026-01-11T19:15:47.037731412-08:00","closed_at":"2026-01-11T19:15:47.037731412-08:00","close_reason":"Spike completed successfully.\n\nObservations:\n1. Worker flow works: spawn → start → work → done → approve → merge\n2. Found and fixed bug: relative worktree paths (skills-5ry7)\n3. Claude (me) completed the task using worker CLI without special prompting\n4. ~7 tool calls to complete simple task\n5. Test script needed sqlite3 in PATH - added check\n\nThe worker system is functional for basic agent tasks."}
|
||||||
{"id":"skills-6ppz","title":"HQ: Dependency deadlocks and task scoping","description":"**Raised by:** flash-or, gpt\n\n**Problem:**\nReal-world coding is rarely perfectly modular. Worker A adds DB field, Worker B needs that field. bd ready is too simple - doesn't detect partial dependencies or cross-cutting changes.\n\n**flash-or:**\n\u003e \"Deadlocks. 'bd ready' is too simple a check. Implement a 'Blocks/Blocked By' metadata in bd. HQ needs to be able to pause Worker B's spawn until Worker A's merge is complete.\"\n\n**gpt:**\n\u003e \"How to split a too-big issue into smaller ones (and who does it). How to handle cross-cutting changes that touch multiple tasks (and merge ordering). Add a 'triage \u0026 slicing' step before spawning.\"\n\n**Suggested fixes:**\n1. Better dependency modeling in bd (partial deps)\n2. Triage \u0026 slicing step before spawn\n3. \"mutex areas\" for shared modules/config\n4. Conflict prediction (recent churn/hot files)\n5. Architectural guardrails for risky areas","status":"open","priority":3,"issue_type":"task","created_at":"2026-01-12T09:25:49.315978432-08:00","created_by":"dan","updated_at":"2026-01-12T09:25:49.315978432-08:00"}
|
{"id":"skills-6ppz","title":"HQ: Dependency deadlocks and task scoping","description":"**Raised by:** flash-or, gpt\n\n**Problem:**\nReal-world coding is rarely perfectly modular. Worker A adds DB field, Worker B needs that field. bd ready is too simple - doesn't detect partial dependencies or cross-cutting changes.\n\n**flash-or:**\n\u003e \"Deadlocks. 'bd ready' is too simple a check. Implement a 'Blocks/Blocked By' metadata in bd. HQ needs to be able to pause Worker B's spawn until Worker A's merge is complete.\"\n\n**gpt:**\n\u003e \"How to split a too-big issue into smaller ones (and who does it). How to handle cross-cutting changes that touch multiple tasks (and merge ordering). Add a 'triage \u0026 slicing' step before spawning.\"\n\n**Suggested fixes:**\n1. Better dependency modeling in bd (partial deps)\n2. Triage \u0026 slicing step before spawn\n3. \"mutex areas\" for shared modules/config\n4. Conflict prediction (recent churn/hot files)\n5. Architectural guardrails for risky areas","status":"open","priority":3,"issue_type":"task","created_at":"2026-01-12T09:25:49.315978432-08:00","created_by":"dan","updated_at":"2026-01-12T09:25:49.315978432-08:00"}
|
||||||
{"id":"skills-6qfe","title":"ui-query: fix argument quoting in wrapper script","status":"closed","priority":3,"issue_type":"bug","owner":"dan@delpad","created_at":"2026-01-15T14:22:04.428356834-08:00","created_by":"dan","updated_at":"2026-01-15T14:23:42.834190743-08:00","closed_at":"2026-01-15T14:23:42.834190743-08:00","close_reason":"Fixed: use printf %q for proper argument escaping"}
|
{"id":"skills-6qfe","title":"ui-query: fix argument quoting in wrapper script","status":"closed","priority":3,"issue_type":"bug","owner":"dan@delpad","created_at":"2026-01-15T14:22:04.428356834-08:00","created_by":"dan","updated_at":"2026-01-15T14:23:42.834190743-08:00","closed_at":"2026-01-15T14:23:42.834190743-08:00","close_reason":"Fixed: use printf %q for proper argument escaping"}
|
||||||
{"id":"skills-6rob","title":"Update code-review skill (The Critic)","status":"open","priority":1,"issue_type":"task","owner":"dan@delpad","created_at":"2026-01-19T14:14:13.643090924-08:00","created_by":"dan","updated_at":"2026-01-19T14:14:13.643090924-08:00"}
|
{"id":"skills-6rob","title":"Update code-review skill (The Critic)","status":"closed","priority":1,"issue_type":"task","owner":"dan@delpad","created_at":"2026-01-19T14:14:13.643090924-08:00","created_by":"dan","updated_at":"2026-01-19T14:40:56.393045914-08:00","closed_at":"2026-01-19T14:40:56.393045914-08:00","close_reason":"Closed"}
|
||||||
{"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"}
|
{"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"}
|
||||||
{"id":"skills-73yu","title":"Validate taskId to prevent path traversal and command injection","description":"[SECURITY] HIGH git.nim:36,37,53,59,89 - taskId used unsanitized in branch names and file paths. If taskId contains '../' or shell metacharacters, could escape worktree dir. Validate taskId matches safe pattern (alphanumeric + dash/underscore only).","status":"closed","priority":1,"issue_type":"bug","created_at":"2026-01-10T19:52:13.24918965-08:00","created_by":"dan","updated_at":"2026-01-10T20:32:28.374723485-08:00","closed_at":"2026-01-10T20:32:28.374723485-08:00","close_reason":"Created utils.nim with common helpers"}
|
{"id":"skills-73yu","title":"Validate taskId to prevent path traversal and command injection","description":"[SECURITY] HIGH git.nim:36,37,53,59,89 - taskId used unsanitized in branch names and file paths. If taskId contains '../' or shell metacharacters, could escape worktree dir. Validate taskId matches safe pattern (alphanumeric + dash/underscore only).","status":"closed","priority":1,"issue_type":"bug","created_at":"2026-01-10T19:52:13.24918965-08:00","created_by":"dan","updated_at":"2026-01-10T20:32:28.374723485-08:00","closed_at":"2026-01-10T20:32:28.374723485-08:00","close_reason":"Created utils.nim with common helpers"}
|
||||||
{"id":"skills-7a00","title":"Add LLM-as-judge verification","description":"Use an LLM to evaluate task completion quality.\n\nComponents:\n- Judge prompt template\n- Rubric format (list of criteria)\n- Scoring mechanism (0-1 per criterion, aggregate)\n- Model selection (haiku for cost, sonnet for quality)\n\nShould take: task description, rubric, code diff/result\nShould output: score, reasoning, pass/fail per criterion","status":"closed","priority":3,"issue_type":"task","created_at":"2026-01-11T16:19:45.933759107-08:00","created_by":"dan","updated_at":"2026-01-11T16:38:26.564395054-08:00","closed_at":"2026-01-11T16:38:26.564395054-08:00","close_reason":"Pausing - need to validate approach with simpler spike first","dependencies":[{"issue_id":"skills-7a00","depends_on_id":"skills-y0p0","type":"blocks","created_at":"2026-01-11T16:20:20.700175136-08:00","created_by":"dan"}]}
|
{"id":"skills-7a00","title":"Add LLM-as-judge verification","description":"Use an LLM to evaluate task completion quality.\n\nComponents:\n- Judge prompt template\n- Rubric format (list of criteria)\n- Scoring mechanism (0-1 per criterion, aggregate)\n- Model selection (haiku for cost, sonnet for quality)\n\nShould take: task description, rubric, code diff/result\nShould output: score, reasoning, pass/fail per criterion","status":"closed","priority":3,"issue_type":"task","created_at":"2026-01-11T16:19:45.933759107-08:00","created_by":"dan","updated_at":"2026-01-11T16:38:26.564395054-08:00","closed_at":"2026-01-11T16:38:26.564395054-08:00","close_reason":"Pausing - need to validate approach with simpler spike first","dependencies":[{"issue_id":"skills-7a00","depends_on_id":"skills-y0p0","type":"blocks","created_at":"2026-01-11T16:20:20.700175136-08:00","created_by":"dan"}]}
|
||||||
|
|
@ -272,14 +272,14 @@
|
||||||
{"id":"skills-v6p","title":"Move Message type from db.nim to types.nim","description":"[COUPLING] LOW db.nim:130-141 - Message type defined in db.nim but other types are in types.nim. Move for consistency.","status":"open","priority":4,"issue_type":"task","created_at":"2026-01-10T18:52:41.927231152-08:00","created_by":"dan","updated_at":"2026-01-10T18:52:41.927231152-08:00"}
|
{"id":"skills-v6p","title":"Move Message type from db.nim to types.nim","description":"[COUPLING] LOW db.nim:130-141 - Message type defined in db.nim but other types are in types.nim. Move for consistency.","status":"open","priority":4,"issue_type":"task","created_at":"2026-01-10T18:52:41.927231152-08:00","created_by":"dan","updated_at":"2026-01-10T18:52:41.927231152-08:00"}
|
||||||
{"id":"skills-vb5","title":"Resolve web search design questions","description":"web_search_brainstorm.md has unanswered design questions: single smart skill vs explicit flags, specific sources priority, raw links vs summaries. Need user input to finalize web-search/web-research direction.","status":"closed","priority":2,"issue_type":"task","created_at":"2025-11-30T11:58:33.482270742-08:00","updated_at":"2025-12-28T22:21:05.814118092-05:00","closed_at":"2025-12-28T22:21:05.814118092-05:00","close_reason":"Resolved: keep 2 skills, web-search for OpenCode only (Claude has built-in), web-research for both. Source filtering via WebSearch domains. Summaries by default."}
|
{"id":"skills-vb5","title":"Resolve web search design questions","description":"web_search_brainstorm.md has unanswered design questions: single smart skill vs explicit flags, specific sources priority, raw links vs summaries. Need user input to finalize web-search/web-research direction.","status":"closed","priority":2,"issue_type":"task","created_at":"2025-11-30T11:58:33.482270742-08:00","updated_at":"2025-12-28T22:21:05.814118092-05:00","closed_at":"2025-12-28T22:21:05.814118092-05:00","close_reason":"Resolved: keep 2 skills, web-search for OpenCode only (Claude has built-in), web-research for both. Source filtering via WebSearch domains. Summaries by default."}
|
||||||
{"id":"skills-vdup","title":"worker CLI: Retry limits and escalation policy","description":"From orch architecture review.\n\nProblem: Agent can enter \"loop of death\" - repeatedly spawning workers that fail.\n\nNeed:\n- Max retries per task before escalation\n- Escalation path (to human? to different agent?)\n- \"Circuit breaker\" pattern at orchestration level\n- Configurable per-task or global limits\n\nRelated: \n- skills-1jc (stuck agent detection)\n- review-gate circuit breaker (exists, 3 attempts)\n\nHQ skill should include: \"If task fails N times, escalate to human\"","status":"open","priority":2,"issue_type":"task","created_at":"2026-01-11T21:12:44.745049544-08:00","created_by":"dan","updated_at":"2026-01-12T10:06:39.334711025-08:00","dependencies":[{"issue_id":"skills-vdup","depends_on_id":"skills-s6y","type":"blocks","created_at":"2026-01-11T21:13:02.95738684-08:00","created_by":"dan"}],"comments":[{"id":4,"issue_id":"skills-vdup","author":"dan","text":"[HQ:merge:2026-01-12T09:36:22-08:00] Merged feedback from skills-gyvt (orch consensus):\n\nPROBLEM (flash-or, gemini, gpt):\nHQ is stateless between sessions. '3 failures then escalate' won't work unless retry count explicitly tracked. Could burn $50 in API credits if HQ/worker loop.\n\nSUGGESTIONS:\n1. worker status returns retry_count\n2. worker request-changes auto-increments counter in state\n3. Global token/cost budget per task ID\n4. Failure categories with different remedies\n5. Hard stop for human intervention regardless of count\n\nOWNER: worker CLI (state machine), not HQ","created_at":"2026-01-12T17:36:22Z"},{"id":13,"issue_id":"skills-vdup","author":"dan","text":"[RECLASSIFY:2026-01-12T10:06:39-08:00] Moved to worker CLI layer. Retry counting is part of worker state machine.","created_at":"2026-01-12T18:06:39Z"}]}
|
{"id":"skills-vdup","title":"worker CLI: Retry limits and escalation policy","description":"From orch architecture review.\n\nProblem: Agent can enter \"loop of death\" - repeatedly spawning workers that fail.\n\nNeed:\n- Max retries per task before escalation\n- Escalation path (to human? to different agent?)\n- \"Circuit breaker\" pattern at orchestration level\n- Configurable per-task or global limits\n\nRelated: \n- skills-1jc (stuck agent detection)\n- review-gate circuit breaker (exists, 3 attempts)\n\nHQ skill should include: \"If task fails N times, escalate to human\"","status":"open","priority":2,"issue_type":"task","created_at":"2026-01-11T21:12:44.745049544-08:00","created_by":"dan","updated_at":"2026-01-12T10:06:39.334711025-08:00","dependencies":[{"issue_id":"skills-vdup","depends_on_id":"skills-s6y","type":"blocks","created_at":"2026-01-11T21:13:02.95738684-08:00","created_by":"dan"}],"comments":[{"id":4,"issue_id":"skills-vdup","author":"dan","text":"[HQ:merge:2026-01-12T09:36:22-08:00] Merged feedback from skills-gyvt (orch consensus):\n\nPROBLEM (flash-or, gemini, gpt):\nHQ is stateless between sessions. '3 failures then escalate' won't work unless retry count explicitly tracked. Could burn $50 in API credits if HQ/worker loop.\n\nSUGGESTIONS:\n1. worker status returns retry_count\n2. worker request-changes auto-increments counter in state\n3. Global token/cost budget per task ID\n4. Failure categories with different remedies\n5. Hard stop for human intervention regardless of count\n\nOWNER: worker CLI (state machine), not HQ","created_at":"2026-01-12T17:36:22Z"},{"id":13,"issue_id":"skills-vdup","author":"dan","text":"[RECLASSIFY:2026-01-12T10:06:39-08:00] Moved to worker CLI layer. Retry counting is part of worker state machine.","created_at":"2026-01-12T18:06:39Z"}]}
|
||||||
{"id":"skills-vex7","title":"Design test-review skill","status":"open","priority":2,"issue_type":"task","owner":"dan@delpad","created_at":"2026-01-19T12:43:42.726113751-08:00","created_by":"dan","updated_at":"2026-01-19T12:43:42.726113751-08:00"}
|
{"id":"skills-vex7","title":"Design test-review skill","status":"closed","priority":2,"issue_type":"task","owner":"dan@delpad","created_at":"2026-01-19T12:43:42.726113751-08:00","created_by":"dan","updated_at":"2026-01-19T14:40:56.382537754-08:00","closed_at":"2026-01-19T14:40:56.382537754-08:00","close_reason":"Closed"}
|
||||||
{"id":"skills-vjm","title":"Refactor update-agent-context.sh: reduce nesting depth","description":"File: .specify/scripts/bash/update-agent-context.sh\n\nIssues:\n- update_existing_agent_file() has 4-level deep nesting (lines 360-499)\n- State machine with multiple variables: in_tech_section, in_changes_section, tech_entries_added\n- 70+ lines of while loop processing\n\nFix:\n- Extract file processing to separate function\n- Consider sed/awk for line-based transformations\n- Use guard clauses to reduce nesting\n\nSeverity: HIGH","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-24T02:50:57.874439288-05:00","updated_at":"2025-12-25T01:44:58.38265672-05:00","closed_at":"2025-12-25T01:44:58.38265672-05:00","close_reason":"update-agent-context.sh is .specify upstream code, not maintained here"}
|
{"id":"skills-vjm","title":"Refactor update-agent-context.sh: reduce nesting depth","description":"File: .specify/scripts/bash/update-agent-context.sh\n\nIssues:\n- update_existing_agent_file() has 4-level deep nesting (lines 360-499)\n- State machine with multiple variables: in_tech_section, in_changes_section, tech_entries_added\n- 70+ lines of while loop processing\n\nFix:\n- Extract file processing to separate function\n- Consider sed/awk for line-based transformations\n- Use guard clauses to reduce nesting\n\nSeverity: HIGH","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-24T02:50:57.874439288-05:00","updated_at":"2025-12-25T01:44:58.38265672-05:00","closed_at":"2025-12-25T01:44:58.38265672-05:00","close_reason":"update-agent-context.sh is .specify upstream code, not maintained here"}
|
||||||
{"id":"skills-vpy","title":"Design checklist support for skills","description":"Design how checklists fit into the skills system.\n\nQuestions:\n- Skill-as-checklist (SKILL.md with just items, no scripts)?\n- Separate checklist format?\n- Trigger conditions in frontmatter?\n- Integration with bd audit for tracking?\n\nTiers considered:\n1. AGENTS.md (simplest, no tracking)\n2. Skill-as-checklist (deployed, invokable)\n3. Proto (full tracking, overhead)","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-23T17:59:09.569427412-05:00","updated_at":"2025-12-29T13:55:35.848981398-05:00","closed_at":"2025-12-29T13:55:35.848981398-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-vpy","title":"Design checklist support for skills","description":"Design how checklists fit into the skills system.\n\nQuestions:\n- Skill-as-checklist (SKILL.md with just items, no scripts)?\n- Separate checklist format?\n- Trigger conditions in frontmatter?\n- Integration with bd audit for tracking?\n\nTiers considered:\n1. AGENTS.md (simplest, no tracking)\n2. Skill-as-checklist (deployed, invokable)\n3. Proto (full tracking, overhead)","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-23T17:59:09.569427412-05:00","updated_at":"2025-12-29T13:55:35.848981398-05:00","closed_at":"2025-12-29T13:55:35.848981398-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-vqm8","title":"TEST: Ambiguity Trap - BlueShield","status":"open","priority":2,"issue_type":"task","owner":"dan@delpad","created_at":"2026-01-12T22:09:45.95727006-08:00","created_by":"dan","updated_at":"2026-01-12T22:09:45.95727006-08:00"}
|
{"id":"skills-vqm8","title":"TEST: Ambiguity Trap - BlueShield","status":"open","priority":2,"issue_type":"task","owner":"dan@delpad","created_at":"2026-01-12T22:09:45.95727006-08:00","created_by":"dan","updated_at":"2026-01-12T22:09:45.95727006-08:00"}
|
||||||
{"id":"skills-vuj2","title":"Add validateTaskId() at CLI entry points","description":"[SECURITY] MED worker.nim - taskId from CLI args used without validation. Add validateTaskId() check in each command. Related to skills-73yu (git.nim validation).","status":"closed","priority":2,"issue_type":"bug","created_at":"2026-01-10T20:12:10.919427534-08:00","created_by":"dan","updated_at":"2026-01-10T20:32:28.382482296-08:00","closed_at":"2026-01-10T20:32:28.382482296-08:00","close_reason":"Created utils.nim with common helpers"}
|
{"id":"skills-vuj2","title":"Add validateTaskId() at CLI entry points","description":"[SECURITY] MED worker.nim - taskId from CLI args used without validation. Add validateTaskId() check in each command. Related to skills-73yu (git.nim validation).","status":"closed","priority":2,"issue_type":"bug","created_at":"2026-01-10T20:12:10.919427534-08:00","created_by":"dan","updated_at":"2026-01-10T20:32:28.382482296-08:00","closed_at":"2026-01-10T20:32:28.382482296-08:00","close_reason":"Created utils.nim with common helpers"}
|
||||||
{"id":"skills-vz05","title":"Agent Coordination: Cross-agent communication and resources","description":"Patterns for coordinating work across multiple agents.\n\nCovers:\n- Cross-agent compatibility (skills that work for any agent)\n- Task specifications and contracts\n- Event notification vs polling\n- Resource budgets (tokens, cost, time)\n- Structured task specs\n\nThese are coordination primitives that HQ and other orchestrators can use.","status":"open","priority":2,"issue_type":"epic","created_at":"2026-01-12T10:04:45.834666795-08:00","created_by":"dan","updated_at":"2026-01-12T10:04:45.834666795-08:00","dependencies":[{"issue_id":"skills-vz05","depends_on_id":"skills-udu","type":"blocks","created_at":"2026-01-12T10:06:28.169956793-08:00","created_by":"dan"},{"issue_id":"skills-vz05","depends_on_id":"skills-0y9","type":"blocks","created_at":"2026-01-12T10:06:28.226270481-08:00","created_by":"dan"},{"issue_id":"skills-vz05","depends_on_id":"skills-4ufc","type":"blocks","created_at":"2026-01-12T10:06:28.270939669-08:00","created_by":"dan"},{"issue_id":"skills-vz05","depends_on_id":"skills-1qz","type":"blocks","created_at":"2026-01-12T10:06:28.325594806-08:00","created_by":"dan"}]}
|
{"id":"skills-vz05","title":"Agent Coordination: Cross-agent communication and resources","description":"Patterns for coordinating work across multiple agents.\n\nCovers:\n- Cross-agent compatibility (skills that work for any agent)\n- Task specifications and contracts\n- Event notification vs polling\n- Resource budgets (tokens, cost, time)\n- Structured task specs\n\nThese are coordination primitives that HQ and other orchestrators can use.","status":"open","priority":2,"issue_type":"epic","created_at":"2026-01-12T10:04:45.834666795-08:00","created_by":"dan","updated_at":"2026-01-12T10:04:45.834666795-08:00","dependencies":[{"issue_id":"skills-vz05","depends_on_id":"skills-udu","type":"blocks","created_at":"2026-01-12T10:06:28.169956793-08:00","created_by":"dan"},{"issue_id":"skills-vz05","depends_on_id":"skills-0y9","type":"blocks","created_at":"2026-01-12T10:06:28.226270481-08:00","created_by":"dan"},{"issue_id":"skills-vz05","depends_on_id":"skills-4ufc","type":"blocks","created_at":"2026-01-12T10:06:28.270939669-08:00","created_by":"dan"},{"issue_id":"skills-vz05","depends_on_id":"skills-1qz","type":"blocks","created_at":"2026-01-12T10:06:28.325594806-08:00","created_by":"dan"}]}
|
||||||
{"id":"skills-w9a4","title":"Design: Garbage collection / janitor for orphaned workers","description":"From orch architecture review consensus.\n\nProblem: Workers can crash, worktrees can hang, locks can be abandoned.\n\nNeed:\n- Detect orphaned worktrees (no heartbeat, stale state)\n- Clean up abandoned locks\n- Prune old/dead worker state from DB\n- Maybe a \"janitor\" that runs periodically or on-demand\n\nRelated: skills-7n4 (rollback strategy), worker staleness detection (exists)\n\nCommands to add:\n- worker cleanup --stale-days=7\n- worker gc (garbage collect)","status":"open","priority":2,"issue_type":"task","created_at":"2026-01-11T21:12:44.530555957-08:00","created_by":"dan","updated_at":"2026-01-11T21:12:44.530555957-08:00","dependencies":[{"issue_id":"skills-w9a4","depends_on_id":"skills-s6y","type":"blocks","created_at":"2026-01-11T21:13:02.689965819-08:00","created_by":"dan"}]}
|
{"id":"skills-w9a4","title":"Design: Garbage collection / janitor for orphaned workers","description":"From orch architecture review consensus.\n\nProblem: Workers can crash, worktrees can hang, locks can be abandoned.\n\nNeed:\n- Detect orphaned worktrees (no heartbeat, stale state)\n- Clean up abandoned locks\n- Prune old/dead worker state from DB\n- Maybe a \"janitor\" that runs periodically or on-demand\n\nRelated: skills-7n4 (rollback strategy), worker staleness detection (exists)\n\nCommands to add:\n- worker cleanup --stale-days=7\n- worker gc (garbage collect)","status":"open","priority":2,"issue_type":"task","created_at":"2026-01-11T21:12:44.530555957-08:00","created_by":"dan","updated_at":"2026-01-11T21:12:44.530555957-08:00","dependencies":[{"issue_id":"skills-w9a4","depends_on_id":"skills-s6y","type":"blocks","created_at":"2026-01-11T21:13:02.689965819-08:00","created_by":"dan"}]}
|
||||||
{"id":"skills-wl2z","title":"Design verify-work skill (The Gatekeeper)","status":"open","priority":1,"issue_type":"task","owner":"dan@delpad","created_at":"2026-01-19T14:14:08.535515645-08:00","created_by":"dan","updated_at":"2026-01-19T14:14:08.535515645-08:00"}
|
{"id":"skills-wl2z","title":"Design verify-work skill (The Gatekeeper)","status":"closed","priority":1,"issue_type":"task","owner":"dan@delpad","created_at":"2026-01-19T14:14:08.535515645-08:00","created_by":"dan","updated_at":"2026-01-19T14:40:56.371833281-08:00","closed_at":"2026-01-19T14:40:56.371833281-08:00","close_reason":"Closed"}
|
||||||
{"id":"skills-wm9","title":"Research Steve Yegge's orchestration work","description":"Steve Yegge is working on something new related to AI orchestration. Research what it is and how it might inform our skills+molecules integration design.\n\nBlocks: skills-hin (ADR finalization)","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-24T02:41:47.848905848-05:00","updated_at":"2025-12-24T02:42:24.40239935-05:00","closed_at":"2025-12-24T02:42:24.40239935-05:00","close_reason":"Not needed - just parking the ADR work"}
|
{"id":"skills-wm9","title":"Research Steve Yegge's orchestration work","description":"Steve Yegge is working on something new related to AI orchestration. Research what it is and how it might inform our skills+molecules integration design.\n\nBlocks: skills-hin (ADR finalization)","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-24T02:41:47.848905848-05:00","updated_at":"2025-12-24T02:42:24.40239935-05:00","closed_at":"2025-12-24T02:42:24.40239935-05:00","close_reason":"Not needed - just parking the ADR work"}
|
||||||
{"id":"skills-wsk7","title":"Add benchmarking metrics collection","description":"Track metrics across runs for comparison:\n\nMetrics:\n- pass_rate (completion)\n- quality_score (LLM judge)\n- cost (tokens in/out)\n- latency (time to complete)\n- efficiency (tool calls, iterations)\n\nDimensions to sweep:\n- model\n- system prompt variant\n- tool configuration\n- context strategy\n\nOutput: structured results (JSON/CSV) for analysis","status":"closed","priority":3,"issue_type":"task","created_at":"2026-01-11T16:19:46.710599693-08:00","created_by":"dan","updated_at":"2026-01-11T16:38:26.601801894-08:00","closed_at":"2026-01-11T16:38:26.601801894-08:00","close_reason":"Pausing - need to validate approach with simpler spike first","dependencies":[{"issue_id":"skills-wsk7","depends_on_id":"skills-y0p0","type":"blocks","created_at":"2026-01-11T16:20:20.844989131-08:00","created_by":"dan"}]}
|
{"id":"skills-wsk7","title":"Add benchmarking metrics collection","description":"Track metrics across runs for comparison:\n\nMetrics:\n- pass_rate (completion)\n- quality_score (LLM judge)\n- cost (tokens in/out)\n- latency (time to complete)\n- efficiency (tool calls, iterations)\n\nDimensions to sweep:\n- model\n- system prompt variant\n- tool configuration\n- context strategy\n\nOutput: structured results (JSON/CSV) for analysis","status":"closed","priority":3,"issue_type":"task","created_at":"2026-01-11T16:19:46.710599693-08:00","created_by":"dan","updated_at":"2026-01-11T16:38:26.601801894-08:00","closed_at":"2026-01-11T16:38:26.601801894-08:00","close_reason":"Pausing - need to validate approach with simpler spike first","dependencies":[{"issue_id":"skills-wsk7","depends_on_id":"skills-y0p0","type":"blocks","created_at":"2026-01-11T16:20:20.844989131-08:00","created_by":"dan"}]}
|
||||||
{"id":"skills-x2l","title":"Investigate hooks for parallel orch queries","description":"When using orch skill, it would be useful to spin off multiple model queries in parallel automatically (e.g., gemini + gpt simultaneously). Explore if Claude Code hooks can trigger parallel background processes when the orch skill is invoked.","status":"closed","priority":2,"issue_type":"feature","created_at":"2025-12-06T19:29:00.165752425-08:00","updated_at":"2025-12-29T15:49:43.831970326-05:00","closed_at":"2025-12-29T15:49:43.831970326-05:00","close_reason":"Investigated. Hooks are synchronous with 60s timeout - unsuitable for background orch queries. Alternatives: (1) SessionStart hook for initial consensus, (2) Explicit skill invocation, (3) PostToolUse for validation. orch consensus already runs models in parallel internally."}
|
{"id":"skills-x2l","title":"Investigate hooks for parallel orch queries","description":"When using orch skill, it would be useful to spin off multiple model queries in parallel automatically (e.g., gemini + gpt simultaneously). Explore if Claude Code hooks can trigger parallel background processes when the orch skill is invoked.","status":"closed","priority":2,"issue_type":"feature","created_at":"2025-12-06T19:29:00.165752425-08:00","updated_at":"2025-12-29T15:49:43.831970326-05:00","closed_at":"2025-12-29T15:49:43.831970326-05:00","close_reason":"Investigated. Hooks are synchronous with 60s timeout - unsuitable for background orch queries. Alternatives: (1) SessionStart hook for initial consensus, (2) Explicit skill invocation, (3) PostToolUse for validation. orch consensus already runs models in parallel internally."}
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue