Back to the Playbook
DefineDE-10
Draft implementation plan
Translate an approved story into a technically grounded implementation approach before any code is written by a person or a coding agent.
Product statusAvailable now
Context in3 required inputsJira story with acceptance criteria · Codebase · Relevant architecture
TransformationEngineer + Engineering Agent + Architecture AgentPlan Drafting · Code Analysis · Atlassian
OutcomeImplementation plan attached to the story.Artifact: Implementation plan
Owner
Engineer
Human + Agent
Participants · Agents
Product ManagerEngineering AgentArchitecture Agent
Trigger
A story is defined and needs technical planning.
Required context
JiraJira story with acceptance criteriaCodeCodebaseArchitectureRelevant architecture
Optional context
ConfluencePRDDesign systemUI draftFilesOwner analysisCodeRelated implementations
Skills
Plan DraftingCode AnalysisAtlassian
Activity steps
- 1Inspect the story and its context.
- 2Trace the affected code and define the changes.
- 3Identify tests, migrations, risks and rollout steps.
- 4Attach the plan to the story.
Output
Implementation plan attached to the story.
Artifacts
Creates: Implementation plan
Updates: Jira story
What good looks like
- Specific enough to guide a person or a coding agent.
- Covers components, tests, risks and rollout.
- Stays implementation-focused.
- Assumptions are listed.
Quality gate
Engineer or tech lead approves for complex work.
Destination
JiraCoding environment
Usually next
People and agents work from the same Product Brain. The owner stays accountable. Assigned agents prepare and check. A named person approves at the gate.
Show us exactly how product work happens today.
Thirty minutes with a founder. We compare your process with the Playbook and pick the first Activity to run on your Jira and your repo.