aboutsummaryrefslogtreecommitdiff
path: root/start-work
Commit message (Collapse)AuthorAgeFilesLines
* refactor: scope start-work refactor audit to every touched fileCraig Jennings2026-04-231-13/+17
| | | | The old "refactor pass" framed the step as a polish over new code. Expanded to "refactor audit" — walks each touched file against the checklist, top to bottom, and every finding lands somewhere: fixed on this branch or filed as a ticket. Drops "skip" as a first-class disposition. Tightens Phase 6 gate 3 to require filed ticket IDs, not just surfaced intent.
* feat(skills): add start-workCraig Jennings2026-04-221-0/+265
A workflow for picking up a specific task (Linear ticket, GitHub issue, todo.org heading, or a described scope) and carrying it through to handoff. Seven phases, three user-approval gates. The phases in order: - Claim: mark in-progress, assign, label, verify project. - Justify (gate 1): benefits, costs, impact, urgency, effort, alternatives, ticket quality. - Approach (gate 2): root cause, risk, test strategy, migration, flag, commit decomposition, branch name. - Implement (TDD): red, green, edge cases, and a refactor pass with a nine-point language-agnostic checklist. - Verify: end-to-end or scripted manual test in the local environment. Playwright for web projects, step-by-step walkthrough for everything else. Never production. - Ready to commit (gate 3): report, deviations from the approach, any follow-ups spotted. - Hand off to the Review-and-Publish flow in commits.md. Cross-referenced from testing.md, commits.md, subagents.md, review-code, brainstorm, arch-design, arch-decide, debug, pairwise-tests, playwright-js, and playwright-py.