{"slug": "ambykit", "title": "Ambykit", "summary": "AmbyKit, a spec-driven development tool for AI coding assistants, launched to let developers author requirements once and emit native commands for multiple assistants including Claude Code, GitHub Copilot, and Cursor. The tool provides a workflow from constitution and specification through design, planning, and implementation, with outputs such as spec.md, design-tokens.json, and tasks.md. AmbyKit aims to eliminate guesswork by enforcing testable requirements and supporting tools like OpenCode and Antigravity.", "body_md": "**Spec-Driven Development for AI coding assistants.** Author your specs, user stories, UI design,\nplans and tasks **once** — AmbyKit emits native commands and rules for every assistant your team\nuses, so the AI builds from clear, testable requirements instead of guessing.\n\nInstall from npm and scaffold AmbyKit into your project:\n\n```\nnpm install -g @ambystech/ambykit\nambykit init            # scaffold .amby/ and pick your assistants\n# — or run it without installing —\nnpx @ambystech/ambykit init\n```\n\nAlready have a project? `init`\n\nis **non-destructive** — an existing `CLAUDE.md`\n\n/`AGENTS.md`\n\nis\npreserved (and backed up); AmbyKit only adds/updates its own `### AmbyKit usage`\n\nsection. Re-run\n`ambykit sync`\n\nany time to keep it current, or `ambykit restore`\n\nto roll a file back.\n\nThen, inside your AI assistant, walk the workflow:\n\n```\n/amby.constitution   # one-time: set your project's guiding principles\n/amby.specify        # describe a feature → spec.md (user stories + EARS requirements)\n/amby.clarify        # resolve open questions\n/amby.revise         # continue an existing spec — add and refine in place\n/amby.design         # UI spec + design-tokens.json\n/amby.plan           # technical plan\n/amby.tasks          # ordered, dependency-aware task list\n/amby.implement      # build it\n```\n\nTrack progress from the terminal:\n\n```\nambykit dashboard\nambykit dashboard 001:US-3   # story ids restart per feature — qualify with the feature ref\n```\n\n📖 Full documentation: [ambystech.io/AmbyKit](https://ambystech.io/AmbyKit/)\n\nAI coding assistants build better software when they start from good requirements. But every\nassistant reads a *different* config format, and specs written for one don't carry to another.\nAmbyKit fixes both: it gives you a rigorous, tech-agnostic SDD workflow **and** a single source of\ntruth that compiles to each tool's native format.\n\n**WHAT before HOW.**`spec.md`\n\ncaptures user stories + testable requirements with no tech decisions;`plan.md`\n\ncaptures the technical approach separately.**UI is a first-class artifact.**`/amby.design`\n\nproduces a UI spec + design tokens — the part most spec tools skip.**Author once, emit per tool.** One neutral source → Claude Code, OpenCode, GitHub Copilot (VS Code + CLI), Cursor (+ CLI), Antigravity (IDE + CLI).\n\n| Phase | Command | Output |\n|---|---|---|\n| Governance (once) | `/amby.constitution` |\n`.amby/constitution.md` |\n| Specify (WHAT/WHY) | `/amby.specify` |\n`specs/NNN-feature/spec.md` |\n| Clarify | `/amby.clarify` |\nresolves `[NEEDS CLARIFICATION]` markers |\n| Revise | `/amby.revise` |\ncontinues `spec.md` / `ui.md` in place |\nDesign (UI) |\n`/amby.design` |\n`ui.md` + `design-tokens.json` |\n| Plan (HOW) | `/amby.plan` |\n`plan.md` (+ `data-model.md` , `contracts/` ) |\n| Tasks | `/amby.tasks` |\n`tasks.md` |\n| Analyze | `/amby.analyze` |\ncross-artifact consistency report |\n| Implement | `/amby.implement` |\nexecutes `tasks.md` |\n\nRequirements use **user stories** (`US-#`\n\n) + **EARS** functional requirements (`FR-###`\n\n) +\n**Given/When/Then** acceptance criteria. Stories carry `priority`\n\nand `depends-on`\n\n/`blocked-by`\n\nso\nwork can be ordered and blocked; `ambykit dashboard`\n\nreports progress across the story/task graph.\n\nClaude Code (CLI + VS Code), GitHub Copilot (VS Code + CLI), OpenCode, Cursor (+ CLI),\nAntigravity (IDE + CLI). See [ docs/tool-compatibility.md](/ambystechcom/AmbyKit/blob/main/docs/tool-compatibility.md).\n\n| Command | Description |\n|---|---|\n`ambykit init [dir]` |\nScaffold `.amby/` , pick tools, emit their files + `AGENTS.md` /`CLAUDE.md` |\n`ambykit add <tool…>` |\nAdd/refresh one tool's integration |\n`ambykit sync` |\nRe-emit all configured tools from the neutral source |\n`ambykit dashboard [story-id]` |\nProgress view over the story/task graph |\n`ambykit analyze` |\nValidate the dependency graph (cycles, blockers, orphans) |\n`ambykit check` |\nDoctor: verify integrations |\n`ambykit restore [file]` |\nRestore an agent-doc file from its `.amby/backups/` backup |\n`ambykit update` |\nUpdate the CLI to the latest, then refresh this project's prompts |\n\nAmbyKit is built with AmbyKit — see [ AGENTS.md](/ambystechcom/AmbyKit/blob/main/AGENTS.md) and\n\n[. MIT licensed.](/ambystechcom/AmbyKit/blob/main/docs/contributing.md)\n\n`docs/contributing.md`", "url": "https://wpnews.pro/news/ambykit", "canonical_source": "https://github.com/ambystechcom/AmbyKit", "published_at": "2026-07-21 19:55:04+00:00", "updated_at": "2026-07-21 20:12:31.991227+00:00", "lang": "en", "topics": ["developer-tools", "ai-tools", "artificial-intelligence"], "entities": ["AmbyKit", "AmbysTech", "Claude Code", "GitHub Copilot", "Cursor", "OpenCode", "Antigravity"], "alternates": {"html": "https://wpnews.pro/news/ambykit", "markdown": "https://wpnews.pro/news/ambykit.md", "text": "https://wpnews.pro/news/ambykit.txt", "jsonld": "https://wpnews.pro/news/ambykit.jsonld"}}