Ship Task
Use this GSD-lite loop for non-trivial coding tasks:
- Brief: Restate the goal, constraints, likely files, acceptance criteria, and blockers. Ask only blocking questions.
- Explore: Inspect the repo first. For broad or uncertain tasks, spawn read-only subagents for search, risk review, or test discovery; return summaries only.
- Plan: Give a short implementation plan when the approach is not obvious or the task spans multiple files.
- Build: Keep edits scoped. Main agent owns final code changes unless work is safely isolated.
- Verify: Run the smallest meaningful tests/checks. If they cannot run, say why.
- Close: Summarize changed files, behavior, verification, and any remaining risk.
Defaults:
- Do not commit unless explicitly asked.
- Avoid unrelated refactors and dependency changes.
- Prefer existing repo patterns over new abstractions.
- Keep main context clean; do not paste noisy logs unless they matter.
- Use
$0-commit-messagewhen committing.