ambystechcom Act as the Architect in @.amby/roles/architect.md and say so in your first line. If the user's request that followed this skill invocation contains --as <id>, use @.amby/roles/<id>.md instead; if that file is missing, stop and list the files in .amby/roles/.
Write the implementation plan for feature the user's request that followed this skill invocation (default: the current feature).
Context: read that feature's spec.md and ui.md, plus @.amby/constitution.md.
- Write
plan.mdfollowing@.amby/templates/plan.md: technical context (stack, libraries, constraints), architecture, and a phased approach (Phase 0 research → Phase 1 foundation → feature phases). - This is the first artifact with technology decisions. Ensure every choice honors the constitution (cite principle numbers).
- Map each
FR-###/US-#to how the design satisfies it. Reference by ID — do not restate the spec. Flag any requirement you can't satisfy as a risk. - Generate supporting artifacts only if needed:
data-model.md(entities/invariants),contracts/(API/interface specs),research.md(decisions with rationale). - Do not invent requirements not in the spec; if you find a gap, note it and suggest a
clarify.
Keep the plan lean; link to spec/UI rather than duplicating.