04-propose
04 propose
Publish your work for review by pushing the branch and creating/updating a Draft PR with a strong title + description.
Guardrails
- Do not implement new code here. If changes are needed, go back to
03-implement. - Do not merge the PR here. Review/merge happens in
05-review. - Prefer Draft PRs by default.
Workflow
More from kelvinz/cobb
compact
Compact `tasks/context.md` by summarising older completed history while preserving active context. Triggers: compact context, prune context log, trim context.
31commit
Create atomic user-approved commits with `feat`/`fix`/`chore` titles. Include inline PRD checklist and context updates per atomic commit. Finalise branch merge/cleanup when requested. Triggers: commit changes, split commits, finalise branch, commit message.
27review
Review the current branch changes for correctness, security, tests, and scope, then return a clear go/no-go decision. Triggers: review, readiness check, pre-commit review, pre-finalise review.
26implement
Implement an existing PRD (`Type: feat`/`fix`/`chore`), update tests/checks, and mark completed PRD checklist items. Triggers: implement prd, build feature from prd, execute prd checklist.
26design
Router-first workflow for high-craft design execution across four modes: ui, ux, motion, and imagery. Use when designing or refining interfaces, structuring and auditing UX/usability/accessibility, implementing or specifying interaction motion, or producing static visual artifacts (.png/.pdf) with a matching philosophy note. Triggers: design ui, improve ux flow, run design audit, add transitions, reduce motion issues, create visual imagery, craft poster composition.
20memory
Maintain durable project memory in `tasks/memory.md` (state, decisions, milestones, gotchas), inline during other workflows or standalone for cleanup/backfill. Triggers: update memory.md, decision log, record project context.
17