actorble-task-runner

name	actorble-task-runner
description	Clarify, execute, mark complete, and commit Actorble implementation tasks from task docs using a TDD-first workflow. Use when Codex is asked to run a task from implementation_tasks.md, implement an Actorble module slice, or continue task execution after a task has been selected.

Actorble Task Runner

Use this skill to execute one Actorble implementation task at a time with clear intent, tests, implementation, and verification.

Workflow

1. Select and understand the task.
   • Read the requested task from the task doc.
   • Read related architecture docs, module READMEs, source files, tests, and AGENTS.md.
   • Inspect git status --short and preserve unrelated user changes.
2. Clarify only high-impact ambiguity.
   • Ask when goal, scope, success criteria, public API, or compatibility constraints are unclear after exploration.
   • Resolve decisions from the task document, architecture docs, ADRs, and existing code before asking.
   • Treat missing pre-task decisions as task-document gaps; ask only if the gap changes public behavior, compatibility, privacy policy, cross-task semantics, user workflow, or acceptance criteria.
   • Use read-only expert subagents only for strict evidence gaps that could otherwise force a high-impact user question or cause a costly wrong implementation.
   • If ambiguity is low impact, make a conservative assumption and report it.
3. Execute with TDD.
   • Add or update the failing Vitest case first.
   • Implement the smallest change that passes.
   • Refactor while keeping tests green.
4. Preserve module boundaries.
   • Follow the dependency map in the task doc.
   • Do not call DOM APIs outside platform adapter modules.
   • Do not merge geometry calculation with interactability judgment.
5. Verify.
   • Run the narrowest relevant tests.
6. Mark the task complete and commit.
   • Update the executed task entry in the task document to show completed status after verification passes.
   • Inspect git status --short and the relevant diff, then stage only task-related changes.
   • Create a conventional commit for the completed task, including the task document status update.
7. Report.
   • Summarize changed files, behavior completed, tests run, commit hash, and residual risk.

Read references/execution-protocol.md before executing a task that changes code.

Defaults

• Use browser/docs/implementation_tasks.md unless the user names another task document.
• Use pnpm commands from the package being changed.
• Prefer behavior-focused tests over snapshot-only tests.
• Respect the active collaboration mode. In Plan Mode, produce an execution plan only and do not mutate files.