agentsclimarketplace

Amby plan

Skill ambystechcom/AmbyKit/.agents/skills/amby-plan

Spec-Driven Development framework that helps AI coding assistants build better software — author your specs, user stories, UI design, plans and tasks once, and emit native config for Claude Code, OpenCode, GitHub Copilot, Cursor, Antigravity and more.

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.

2 things to look at

  • 29 days oldThe repository was created 29 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 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.

What its author says it does

Copied from the file, not written here

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

SKILL.md

1.2 KB, as published. Nobody here has run it

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

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.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.