# Amby Plan

> Produce the technical implementation plan (the HOW) from an approved spec and UI.

- Skill: `ambystechcom/amby-plan` (Agent Skill)
- Install (CLI): `npx skillmds@latest add ambystechcom/amby-plan`
- Raw SKILL.md: https://api.skillmd.com/api/skills/ambystechcom/amby-plan/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: ambystechcom (https://skillmd.com/u/ambystechcom)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/ambystechcom/amby-plan

---

<!-- GENERATED by AmbyKit from src/prompts/plan.md — do not edit by hand; run `ambykit sync`. -->

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`.

1. Write `plan.md` following `@.amby/templates/plan.md`: technical context (stack, libraries,
   constraints), architecture, and a phased approach (Phase 0 research → Phase 1 foundation → feature phases).
2. This is the **first artifact with technology decisions.** Ensure every choice honors the
   constitution (cite principle numbers).
3. 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.
4. Generate supporting artifacts only if needed: `data-model.md` (entities/invariants),
   `contracts/` (API/interface specs), `research.md` (decisions with rationale).
5. 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.