planning-workflow

Plugin planning-workflow from marketplace mistakenot-skills in mistakenot/skills. Commands read from the repo's manifest — 20 days ago.

Skills (20)

• address-feedback

  Works through all open PR review threads by fixing code, replying to reviewers, and resolving threads. Use when 'address feedback', 'fix PR comments', 'resolve review threads', or after a code review has left feedback on the PR.

• code-review

  Performs a structured code review of changes with severity labels covering correctness, security, performance, error handling, testing, and architecture. Use when 'code review', 'review this PR', 'review changes', or when a structured review of implementation changes is needed.

• commit-task

  Verifies completeness of all planning docs and commits them to main. Use when 'commit the task', 'finalize the task', 'commit task docs', or after all planning docs have been reviewed and approved. Not applicable when implementation has already started or for committing code changes.

• complete-task

  Finalizes a feature branch and merges it to main. Addresses remaining PR feedback, runs tests, writes feedback.md, merges the PR, exits the worktree, and verifies the merge. Use when 'complete task', 'finalize and merge', 'ship this task', or when the feature branch is ready to ship.

• delegate-task

  Dispatches /execute-task for a planned task to a fresh background worker (herdr), freeing this session. Use when 'delegate task', 'send to executor', 'hand off this task'.

• delegate

  Hands a freeform prompt to a fresh background coding agent (herdr) — a worker in its own worktree, or a planner on main. Use when 'delegate this', 'send to an executor', 'run this in background', 'spin up a planner'. Not for planned tasks with docs (use delegate-task).

• execute-task

  Autonomously implements a planned task end-to-end using the coordinator-subagent pattern. Reads task docs, creates a worktree, dispatches subagents per phase, tracks progress, and opens a PR. Use when 'execute task', 'implement task', or after planning docs have been committed.

• new-epic

  Plans an epic.html: user-facing direction, guard rails, and a breakdown into deployable, sequenced tasks. Use when 'new epic', 'create epic', 'plan an epic'. Not for a single task (use new-task).

• new-plan

  Writes the Plan tab and backfills AC traceability for a task. Use when 'write a plan', 'new plan', 'create the plan', 'plan the task', or after solution is approved. Not applicable when solution doesn't exist yet.

• new-solution

  Gathers context, writes Verification and Solution tabs for a task. Use when 'write a solution', 'design the solution', 'new solution', 'explore approaches', or after requirements have been approved. Not applicable when requirements don't exist yet.

• new-task-quick

  Plans a task end-to-end in one unattended pass: Requirements, Verification, Solution and Plan tabs, pauses only for open questions, then Codex-reviews the answered doc. Use when 'new task quick', 'quick task', 'plan end-to-end'. Not for stage-by-stage review (use new-task).

• new-task

  Creates a plan.html with Requirements tab for a new task. Use when 'create a task', 'new task', 'start a task', 'write requirements', or when a user describes a feature/fix to plan. Not applicable when executing an existing task, reviewing existing docs, or planning every stage unattended (use new-t

• request-claude-review

  Runs a Claude Code review of task planning docs or any files (code, markdown, config), then resolves its comments. Use when 'request claude review', 'claude review task 042', 'have claude review <file>'.

• request-codex-review

  Runs a Codex review of task planning docs or any files (code, markdown, config), then resolves its comments. Use when 'request codex review', 'codex review task 042', 'have codex review <file>'.

• request-council-review

  Runs a parallel Claude, Codex and Grok council review of task planning docs or any files, merges de-duplicated comments, then resolves them. Use when 'council review', 'review with all three'. Not for one reviewer (use request-codex-review).

• request-grok-review

  Runs a Grok CLI review of task planning docs or any files (code, markdown, config), then resolves its comments. Use when 'request grok review', 'grok review task 042', 'have grok review <file>'.

• resolve-comments

  Resolves review comment threads — inline in planning docs/markdown/HTML or in .review.md sidecars — by fixing, rejecting, or escalating. Use when 'resolve comments', 'address comments', 'fix review comments', or after a review. Not for PR feedback (use address-feedback).

• review-task

  Reviews task planning docs or any files (code, markdown, config) and leaves structured comment threads. Use when 'review task docs', 'review the plan', 'review task 042', 'review <file> and leave comments'. Not for PR/diff review (use code-review).

• status-report

  Reports what every background worker is doing (herdr), flags unhealthy ones, and reaps finished ones. Use when 'status report', 'check executors', 'executor status', 'how are tasks going'.

• task-feedback-analyser

  Extracts recurring patterns from completed task feedback into generalizable workflow rules. Scans feedback.md files and review threads, clusters by theme, and drafts rules with a strict 3-example minimum. Use when 'analyse feedback', 'extract rules', 'find patterns in feedback', or when reviewing hi

Similar plugins