What problem does it solve? When a task branch is finished, teams often leave stale task folders on disk, lose the owner's original decisions, and let post-merge review findings fall through the cracks. This Skill defines the exact closing procedure: how to take a task folder apart before the PR opens, how to audit the work queue, and where background rules-review findings must land so nothing is lost. ## Core Features & Use Cases - Task folder teardown: Splits a finished task folder into three outcomes — standing requirements promoted to the rules layer, the decision story moved to docs/archive/, and the rest deleted — executed as the last commit before the PR opens. - Work queue audit: Runs npm run check:board, npm run check:specs, and npm run check:docs to catch closed-task folders, abandoned drafts, and broken doc paths in the same turn. - Background rules review: Launches a closed-task review role right after the PR opens, gathers the digest first, and writes returned findings into a <plan name>-findings.md file next to the epic plan. - Use Case: After merging a feature branch, an agent archives grill.md to docs/archive/, deletes the task folder, runs the three audits, opens the PR as a draft, and launches the rules review in the background while starting the next task. ## Quick Start Take apart the finished task folder, run the work queue audits, and open the PR following the task-flow-archive pattern.
