spec-planninglisted

# Spec Planning Plan the implementation of the named feature. When invoked, determine the feature name from the user's request; if it is not provided, ask before proceeding. ## Inputs to read Feature specs: - NFRs: `features/<feature_name>/nfrs.md` - Acceptance: `features/<feature_name>/acceptance.feature` Architecture standards: - `docs/backend/architecture/` (all files) Evaluation standards: - `docs/backend/evaluation/eval_criteria.md` Existing artifacts (read if present, update if needed): - `features/<feature_name>/eval_criteria.yaml` ## Instructions 1. Read all inputs listed above. 2. Summarize the business goal and scope of the feature. 3. Identify required design elements aligned to Hexagonal Architecture: - Inbound ports (`ports/inbound/`) - Domain logic modules (`services/`) - Outbound ports (`ports/outbound/`) - Adapters (`adapters/`) - API route entrypoints (`api/`) 4. Flag any deviation from architecture contracts: - `ARCH_CONTRACT.md`, `BOUNDARIES.md`, `API_CONVENTIONS.md`, `SECURITY_AUTH_PATTERNS.md` 5. Determine ADR need. Mark **ADR required** if any of these occur: - New outbound dependency or external integration - Boundary change or exception - New pattern or approach not already documented ## Output A: Plan Write `features/<feature_name>/plan.md` with: - Task checklist (files/modules to create or edit) - Test plan (unit, integration, contract) - LLM eval hooks and where they run - Risks, open questions, and follow-ups -