Template: Implementation Plan [Project Name]

Author: Principal Engineer Date: YYYY-MM-DD Status: Draft | In Review | Approved Related Issue: [GitHub Issue link]

Summary

One-paragraph description of what this plan covers and why the change is needed.

Context

• Link to the originating Product Owner feature description or user story.
• Link to the Domain Architect model if new entities or relationships are involved.
• Any relevant prior art, spikes, or architecture decision records.

Scope

In Scope

• List of specific changes this plan covers.

Out of Scope

• Explicitly list what this plan does not cover, to prevent scope creep.

Design

Describe the technical approach at a level sufficient for the Back End Engineer or Front End Engineer to implement without making architectural decisions.

Persistence Changes

• New tables, columns, Flyway migration scripts.
• Changes to Exposed table definitions.

Service Layer Changes

• New or modified DataAuthorityService implementations.
• Observer registrations, cascade behavior, validation rules.

API Changes

• New or modified endpoints (method, path, request/response shapes).
• Changes to DataAuthorityEndpoint or ServiceEndpointDsl usage.

Frontend Changes

• New pages, components, or layouts.
• State management, data fetching, and mock handler changes.

Task Breakdown

#	Task	Persona	Depends On	Acceptance Criteria
1	Create Flyway migration	Back End Engineer	—	Migration applies cleanly
2	Add Exposed table definition	Back End Engineer	1	Compiles; maps to new schema
3	Implement service logic	Back End Engineer	2	Unit tests pass
4	Add API endpoint	Back End Engineer	3	Endpoint responds correctly
5	Implement frontend page	Front End Engineer	4	Page renders; calls API
6	Write acceptance tests	Acceptance Test Engineer	4, 5	Bruno API tests pass

Worktree Strategy

When the task breakdown has 2+ parallel agents modifying the same repository, each agent should work in its own git worktree for physical directory isolation. If worktrees are not needed (single agent, or tasks target different repositories), replace this section with: “Single directory — no worktrees needed.”

Base branch: <branch-name>

Worktree layout (at workspace root):

Worktree directory	Branch	Agent	Task
${projectName}-worktrees/${taskName}	${githubUsername}/${projectName}/${taskName}	[agent name]	#

Merge workflow: [Describe how branches integrate before final validation.]

Agent absolute-path rule: Agents in worktrees MUST use absolute paths for all tool calls and prefix Bash commands with cd <worktree-absolute-path> &&.

Risks and Mitigations

Risk	Likelihood	Impact	Mitigation
Migration conflicts with concurrent work	Low	High	Coordinate migration version numbers via Team Lead

Open Questions and Decisions

#	Question	Options	Recommendation	Decision