Workflows Overview
Pick a playbook by what you are starting from: a Jira ticket, a spec, a PRD, a design file, or nothing at all.
A workflow is an end-to-end playbook for a scenario that has its own starting material. If you just want to build, fix, review, or ship something, you want a guide instead. Those are shorter, and there is one per task.
Start from what you have
| What is in front of you | What you want out of it | Playbook |
|---|---|---|
| A Jira ticket | A merged PR | Ticket to Code |
| A Jira ticket | To know whether it is ready to work on, and how big | Ticket Evaluation |
| A ticket with screenshots, video, or a Figma link | Implementation that matches the design | Ticket with Media |
| A Confluence spec | A planned sprint | Spec to Sprint |
| A Confluence spec | A merged PR, with every step explained | Spec to PR: Behind the Scenes |
| A PRD or a pile of incoming requests | Analysed, triaged, estimated work | PRD Intake |
| A sprint and a team | Sprint goal, DoR/DoD, retro actions, spike governance | Agile / Scrum |
| Commit history | A retrospective people will read | Sprint Retrospective |
| An empty directory | A working MeowKit project | Starting a New Project |
| Somebody else's undocumented codebase | Enough understanding to change it safely | Maintaining Old Projects |
If the input to your task is "the code I already have", you are almost certainly looking for a guide rather than a workflow.
Scenario notes
Shorter pages for work that has no special starting material: the approach, and which skills to reach for.
| Scenario | Page |
|---|---|
| Assess security across OWASP, STRIDE, supply chain, platform | Security Audit |
| Write unit and E2E tests | Writing Tests |
| Manual QA and generating Playwright specs | QA Testing |
| Decide an architectural trade-off and record it | Architecture Decisions |
| Frontend work with the UI/UX standards applied | Frontend Development |
| Restructure code without changing behaviour | Refactoring |
| Keep project documentation in step with the code | Documentation |
| Evaluate a library or approach before committing | Researching Libraries |
The everyday tasks
These moved to guides, because they are things you do rather than playbooks you follow:
Build a feature · Fix a bug · Review code · Ship safely · Autonomous build