Amby plan

Produce the technical implementation plan (the HOW) from an approved spec and UI.From its SKILL.md

Install

npx -y skills add ambystechcom/AmbyKit --skill amby-plan

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

1.2 KB, 278 tokens by cl100k_base, as published. Nobody here has run it

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.md following @.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.

Read from the repository

Just SKILL.md. No reference files, no scripts.