Menü
QA failed — move ticket back to In Progress. Branch is retained; developer resumes work on it. Use when QA finds issues that need fixes before re-review.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Explore the codebase and write a discovery brief. Use when discovering scope, surveying a codebase, or starting a feature.
QA passed — merge branch to main, move ticket to Done, delete branch. Use after QA sign-off on a completed feature.
Run one fully-autonomous development iteration. Picks a ticket (from --focus or backlog via ideator), then runs the `orchestrator autopilot <slug>` workflow subcommand. This skill should be used when the user says 'autopilot', 'autonomous', 'self-improve'.
Create commits in logical groups. This skill should be used when the user says 'commit-group', 'group commits', 'organize commits', or when there are multiple unstaged changes that should be organized into atomic commits.
Complete feature — verify, signoff, archive. Runs only the complete phase of the orchestrate workflow. This skill should be used when the user says 'complete feature', 'finish feature', 'merge to main'.
Fetch curated, agent-optimized library documentation via Context Hub (chub). Use when implementing features that use external libraries, when Context7 returns noisy/incomplete docs, when you need language-specific or version-specific API docs, or when the user says "chub", "context hub", "get docs for X". Prefer this over Context7 for libraries in chub's registry — curated docs have less noise and better code examples.
| name | rework |
| description | QA failed — move ticket back to In Progress. Branch is retained; developer resumes work on it. Use when QA finds issues that need fixes before re-review. |
| user-invocable | true |
| args | [{"name":"change-id","description":"Change ID (e.g. orc-86).","required":true}] |
There is no orchestrator rework workflow. Move the ticket back to In Progress
yourself and leave a comment explaining what failed QA. The feature branch and
worktree stay intact — the developer resumes on the same branch.
Backlog.md
backlog task edit <ticket-id> -s "In Progress"
backlog task comment <ticket-id> "QA failed: <summary of issues>"
Linear — use /linear to set status to In Progress and add a comment with the
QA findings.
Do not delete the branch or worktree. After fixes, the developer re-runs the
workflow from the existing branch (typically orchestrator feature <slug> or
/run-implement or orchestrator run … --schema implement to continue implementation).