@dirtydishes/skills 0.1.1

package/skills/dirtyloops/templates/workflows/orchestrator-callback/implementation-thread-prompt.md.template

@@ -0,0 +1,40 @@
+# Implementation Thread Prompt
+
+You are the implementation thread for Beads issue `{{PHASE_ISSUE_ID}}`.
+
+Callback target:
+
+`{{ORCHESTRATOR_THREAD_ID}}`
+
+You must send your final callback to the exact orchestrator thread id `{{ORCHESTRATOR_THREAD_ID}}`. Do not interpret this as `current orchestrator thread`, `this thread`, or any implicit wrapper metadata.
+
+## Inputs
+
+- Beads issue: `{{PHASE_ISSUE_ID}}`
+- Phase doc: `{{PHASE_DOC}}`
+- Implementation index: `{{IMPLEMENT_MD}}`
+- Turn doc: `{{TURN_DOC}}`
+- Branch/worktree instructions: `{{BRANCH_WORKTREE_INSTRUCTIONS}}`
+- Thread default: standard speed/reasoning unless the orchestrator prompt explicitly says otherwise
+
+## Rules
+
+- Implement exactly this phase.
+- Do not widen scope.
+- Use bounded implementation/scout subagents when useful.
+- Update the existing Markdown turn doc.
+- Run local gates before PR when feasible.
+- Open or update the PR.
+- Do not create the review thread.
+- Call back exactly once to the orchestrator.
+- The callback payload must include `orchestrator_thread_id: "{{ORCHESTRATOR_THREAD_ID}}"` and your `source_thread_id`.
+
+## Callback States
+
+Call back only when:
+
+- PR is open and ready for review
+- task is complete but PR cannot be created, with exact blocker
+- genuinely blocked
+
+Use the implementation callback schema from `schemas/implementation-callback.schema.json`.

package/skills/dirtyloops/templates/workflows/orchestrator-callback/review-thread-prompt.md.template

@@ -0,0 +1,38 @@
+# Review Thread Prompt
+
+You are the review thread for Beads issue `{{PHASE_ISSUE_ID}}`.
+
+Callback target:
+
+`{{ORCHESTRATOR_THREAD_ID}}`
+
+You must send your final callback to the exact orchestrator thread id `{{ORCHESTRATOR_THREAD_ID}}`. Do not interpret this as `current orchestrator thread`, `this thread`, or any implicit wrapper metadata.
+
+## Mandatory Skill
+
+Use:
+
+`thermo-nuclear-code-quality-review`
+
+## Inputs
+
+- Beads issue: `{{PHASE_ISSUE_ID}}`
+- Phase doc: `{{PHASE_DOC}}`
+- Turn doc: `{{TURN_DOC}}`
+- PR: `{{PR_URL_OR_ID}}`
+- Branch/commit: `{{BRANCH_OR_COMMIT}}`
+- Required gates: `{{QUALITY_GATES}}`
+- Thread default: standard speed/reasoning unless the orchestrator prompt explicitly says otherwise
+
+## Rules
+
+- Be ambitious about structural simplification.
+- Use reviewer and CI verification subagents when useful.
+- Own CI through green, repaired-and-green, unavailable-with-evidence, or blocked-with-cause.
+- Apply safe in-scope repairs when assigned by the orchestrator prompt.
+- Update the existing Markdown turn doc.
+- Do not create follow-up implementation threads.
+- Call back exactly once when review and CI are resolved.
+- The callback payload must include `orchestrator_thread_id: "{{ORCHESTRATOR_THREAD_ID}}"` and your `source_thread_id`.
+
+Use the review callback schema from `schemas/review-callback.schema.json`.

package/skills/dirtyloops/templates/workflows/orchestrator-callback/run-loop-addendum.md.template

@@ -0,0 +1,17 @@
+## Orchestrator Callback Workflow
+
+This loop uses a main orchestrator thread plus separate implementation and review threads.
+
+- Only the orchestrator creates implementation and review threads.
+- The orchestrator passes its concrete thread id as the callback target.
+- Before launching a worker or reviewer, verify the actual prompt text includes that exact thread id and does not rely on generic wording like `current orchestrator thread` or `this thread`.
+- Worker and reviewer threads default to standard speed/reasoning unless Beads loop metadata explicitly overrides it.
+- Implementation threads update the existing phase turn doc, open the PR, and call back exactly once when PR-ready or blocked.
+- Implementation callback payloads must echo `orchestrator_thread_id` and include `source_thread_id`.
+- Implementation threads do not create review threads.
+- Review threads use `thermo-nuclear-code-quality-review`.
+- Review threads own CI, repairs, reruns, and evidence.
+- Review threads update the existing phase turn doc and call back exactly once when review and CI are resolved.
+- Review callback payloads must echo `orchestrator_thread_id` and include `source_thread_id`.
+- The orchestrator owns Beads closeout and next selector launch.
+- Use a fallback heartbeat around 30 minutes for long-running threads.

package/skills/dirtyloops/templates/workflows/single-thread-subagent/run-loop-addendum.md.template

@@ -0,0 +1,12 @@
+## Single-Thread Subagent Workflow
+
+This loop runs in one visible Codex coordinator thread. Single-thread means one coordinator, not solo implementation.
+
+- Do not create separate Codex worker or reviewer threads.
+- Use selector, scout, slice-planning, implementation-helper, reviewer, and CI subagent swarms inside this thread.
+- Use 8+ subagents by default for broad scout, slice, implementation-helper, and review work. If fewer than 8 are used for a broad phase, record why in the turn doc.
+- Before broad implementation, run a slice planning swarm and synthesize the slice plan into the turn doc.
+- The main thread owns integration, branch state, PR state, Beads updates, and closeout.
+- Subagents inspect, compare, critique, split the phase into slices, prepare implementation guidance or patches, verify, and report.
+- Subagents do not own loop state.
+- The coordinator may implement glue, integration, conflict resolution, and final repairs. It must not do most broad discovery or implementation itself.