commit-task

Commit Task

Verify completeness of all planning docs and commit them to main. This is the final planning stage -- it does NOT create a feature branch or start implementation.

Part of the task planning workflow. See references/workflow-overview.md for the full pipeline.

Process

Step 1: Identify Task

Find the active task from user input or recent context. Locate the task folder under docs/tasks/$ID-$NAME/.

Step 2: Verification Checklist

All checks must pass before committing:

• All 4 files exist: requirements.md, solution.md, context.md, plan.md
• No unanswered Open Questions: check Open Questions sections in requirements.md and plan.md -- all must be resolved or empty
• All ACs addressed: every acceptance criterion in requirements.md has corresponding test coverage in solution.md and plan steps in plan.md
• Plan consistent with solution: the approach in solution.md matches the phases and steps in plan.md
• Context covers plan references: files and patterns referenced in plan.md are documented in context.md
• No unresolved P1 comments: if review comments exist, no UNRESOLVED(P1) threads remain
• Epic frontmatter consistent: if any doc has epic: frontmatter, all four docs have the same value

If any check fails, report the failures and stop. Do not commit incomplete docs.

Step 3: Advance status to pending

The planning docs are complete and about to be committed — advance the task to the pending stage (awaiting execution). See references/task-status.md: set status: pending in plan.md frontmatter (markdown task) or status="pending" on <pd-doc> in plan.html (HTML/beta task). Stage this change with the docs.

Step 4: Commit and Push

git add docs/tasks/$ID-$NAME/*
git commit -m "docs(tasks): add task $ID-$NAME planning docs"

After committing, push to origin:

git push origin main

If the push fails because the local branch is behind origin:

1. Try git pull --rebase origin main then git push origin main
2. If the rebase fails (conflicts), abort with git rebase --abort and try git pull --no-rebase origin main then git push origin main
3. If that also fails, stop and ask the user for help — do not force-push or discard changes

Step 5: Next Steps

After successful push, tell the user:

"Task $ID planning docs committed and pushed to main. To begin implementation, run /execute-task $ID."

Do NOT create a feature branch. Do NOT start implementation.

Commit Conventions

See references/commit-conventions.md for commit message format and rules.