implementation-plan

name	implementation-plan
description	Generate an ordered implementation checklist with evaluation compliance summary from a validated preflight

Implementation Plan

You are writing an evaluation-driven implementation plan for a feature. Determine the feature name from the user's request; if it is not provided, ask before proceeding.

Inputs

Read these artifacts before planning:

• features/<feature_name>/nfrs.md
• features/<feature_name>/acceptance.feature
• features/<feature_name>/eval_criteria.yaml
• features/<feature_name>/architecture_preflight.md
• docs/backend/evaluation/eval_criteria.md
• docs/backend/architecture/ (all files)

Planning Requirements

The plan must:

• Follow Hexagonal Architecture (ports + adapters)
• Enforce FIRST principles for unit tests
• Enforce 7 Code Virtues for implementation
• Respect all boundary and dependency contracts
• Align with feature-specific eval thresholds

Output Format

Feature Summary

• Business goal, user value, success criteria

Architecture Mapping

Identify inbound ports, domain services, outbound ports, adapters, and API routes. Explicitly confirm no boundary violations.

Task Breakdown (Ordered Checklist)

List all implementation steps in order. Each step must:

• Specify files/modules touched
• Reference the spec or architectural rule driving it
• Reference which FIRST principle it supports (if test-related)
• Reference which Code Virtue is at risk
• Mark with ADR required flag if applicable

Test & Evaluation Plan

• How FIRST will be satisfied (mocking and isolation strategy)
• Simplicity and duplication risks
• LLM evaluation dimensions from eval_criteria.yaml and CI gate expectations

Evaluation Compliance Summary

Predict before implementation begins:

• Expected FIRST average score (0–5) and justification
• Expected 7 Virtue average score (0–5) and justification
• Identified refactor triggers likely to occur
• Confirmation that eval_criteria.yaml thresholds are satisfied by design

If predicted averages are below required thresholds, adjust the plan before proceeding.

Refactor Triggers

List conditions under which refactoring must occur:

• Duplication detected
• Complexity threshold exceeded
• FIRST or Virtue score below threshold

Risks & Unknowns

Missing constraints, integration risks, performance concerns, security implications.

---

Do not generate implementation code. Plan must be executable as-is.