AthenodeAthenode

Spec-driven development

Specify, decompose, and ship — with your AI agent.

Athenode turns one product spec into a detailed mind map, breaks it down into leaf specs, and hands each one to an AI agent to implement — all driven from the CLI you already use.

Start for free
npx @athenode/cli init
AI Agent
›/mindmap-specification I want to add a checkout flow
•spec-placement-researcher · Find the best place in the tree└Done (9 tool uses · 14.2k tokens)
•spec-feasibility-analyst · Check feasibility against the code└Done (21 tool uses · 38.5k tokens)
•spec-dependency-researcher · Look for dependencies and overlaps└Done (12 tool uses · 19.8k tokens)
•User answered the agent's questions:└· Should guest checkout skip account creation entirely, or offer it as an optional step? → Optional account step└· Do we need saved payment methods for returning users, or only one-time card entry for now? → One-time card entry
•User answered the agent's questions:└· Which topic should we explore next? → Addresses & shipping
•User answered the agent's questions:└· Should shipping and billing addresses share one form, or stay as two separate steps? → Two separate steps└· How should shipping cost be calculated — a flat rate, or live carrier rates? → Flat rate, but free shipping over $50
•User answered the agent's questions:└· Which topic should we explore next? → Finish the mind map
•Synthesized the answers into one specification — "Checkout flow" is prepared.
•User answered the agent's questions:└· What should happen with "Checkout flow" next? → Decompose into stages
•spec-decomposer · Propose stages for "Checkout flow"└Done (17 tool uses · 29.4k tokens)
•User answered the agent's questions:└· Split "Checkout flow" into 3 stages — Cart, Payment, Shipping? → Yes, create these as drafts
•Created 3 draft stages with their clarifying questions.
•User answered the agent's questions:└· Should quantity changes update totals live, or only on an explicit "Update cart" click? → Update totals live└· Should a declined card retry in place, or send the user back to the cart? → Retry in place└· Should each order ship to a single address, or allow split shipments? → Single address
•spec-decomposition-finalizer · Finalize 3 stages└Done (26 tool uses · 44.1k tokens)
•Finalized 3 stages — Cart, Payment, Shipping — each prepared and linked in build order.
•User answered the agent's questions:└· What should happen with "Checkout flow" next? → Apply now
•Applying "Checkout flow" — 3 stages in build order.
•spec-implementation-planner · Plan "Cart"└Done (14 tool uses · 31.2k tokens)
•spec-implementer · Implement "Cart"└Done (23 tool uses · 48.7k tokens)
•spec-implementation-planner · Plan "Payment"└Done (12 tool uses · 27.9k tokens)
•spec-implementer · Implement "Payment"└Done (27 tool uses · 55.3k tokens)
•spec-implementation-planner · Plan "Shipping"└Done (11 tool uses · 24.6k tokens)
•spec-implementer · Implement "Shipping"└Done (19 tool uses · 41.8k tokens)
•spec-implementation-reviewer · Review 3 implemented leaves└Done (31 tool uses · 62.4k tokens)
•"Checkout flow" is completed — 3 stages implemented, reviewed and committed.└CartTotals update live as quantities change; guests can create an account as an optional step.└PaymentOne-time card entry; a declined card retries in place without losing the cart.└ShippingSeparate shipping and billing steps, one address per order, flat rate with free shipping over $50.└Review3 of 3 stages approved, no open findings└Tests48 passed, 0 failed└Files✎ 7 changed, ✚ 4 created└Git3 commits on feature/checkout-flow
›Try "/mindmap-specification <idea>"

Features

From first question to shipped feature

Give your AI agents a clear spec instead of a vague prompt, and get exactly what you meant.

  1. Clarify the spec

    Answer a few questions, get a clear spec

    AI asks the right questions and turns your answers into a clear spec.

    • The agent asks what's missing, so nothing is left to guesswork
    • Every answer lands in a living mind map
  2. Plan the build order

    Always know what to build next

    Specs are linked by their blockers, so agents only pick up work that's ready to start.

    • Blockers between specs set the build order
    • Blocked specs wait until what they depend on is done
  3. Ship with AI

    Ship every piece with the agent you trust

    Your AI agents build them in parallel while you track every result.

    • Works with Claude Code, Cursor, Codex and more
    • Every change is recorded against its spec

Decomposition in depth

Start with an idea. Go as deep as you need.

Capture the big picture first, then break each spec into smaller ones, level by level, until every leaf is small enough for an agent to implement in one run.

  • Referral rewards program
    • Referral link generation
      • Unique invite codesReady
      • Share buttons on the profile pageReady
    • Reward payout rules
      • Qualifying purchase checks
        • Minimum order amountReady
        • Refund clawback windowReady
      • Crediting the account balance
        • Ledger entry per rewardReady
        • Reward notification emailReady
    • Referral stats dashboard
      • Invites and conversions chartReady
      • Export to CSVReady

Integrations

Works with 9 AI coding tools

Athenode exports your agents, skills, rules and MCP servers to 9 AI coding tools, from Claude Code, Cursor and Codex to GitHub Copilot, Kiro and more — straight from the CLI, no manual setup.

See what each tool gets

Your setup

Your setup, your rules

Every project gets its own agent setup — the agents, skills, MCP servers and rules your AI tools work with. Start from ours, make it yours, share it with the team.

  1. Start from the default

    Each project gets its own copy of the Athenode setup, ready from day one.

  2. Make it yours

    Clone it, then add or remove agents, skills, MCP servers and rules.

  3. Share it with your team

    Everyone on the project works with the same setup, kept in one place.

Autonomous execution

Your spec tree keeps moving

Athenode understands how specs depend on one another, then continues through the next implementation-ready leaf — autonomously.

Athenode completed 3 specs overnight while tracking dependencies automatically.

Pricing

Start free. Scale when your team does.

Every plan runs the full spec-driven workflow. Upgrade for unlimited specs, more agent setups and your whole team working from one spec tree.

Included in every plan

  • Spec tree with mind-mapping and decomposition
  • AI agents implement leaf specs end to end
  • Export to Claude Code, Codex, Cursor and more
  • Real-time progress tracking for every spec
Compare all plan limits
Compare plans
FeatureFreeSoloTeamBusiness
Free projects per user3Not applicableNot applicableNot applicable
Project members (incl. owner)1 (owner only)1 (owner only)1050
Invites, editor/viewer rolesNoNoYesYes
Specifications per project100UnlimitedUnlimitedUnlimited
Agent setups per project1510Unlimited
Skills per setup53050Unlimited
Agents per setup103050Unlimited
MCP servers per setup31530Unlimited
CLI tokens per user per project1101020
API requests per minute per project (CLI)603006001200
Priority supportNoNoNoYes

FAQ

Common questions

An agent setup is the configuration of your AI agents, skills, MCP servers and AGENTS.md for a project — created and customised by anyone on the team, then shared with every project member so everyone works from the same configuration.

No. The CLI writes its content into a block between Athenode markers, and everything outside that block stays exactly as you wrote it. MCP servers are merged into your existing configs rather than replacing them. If the markers are broken, the CLI stops with an error and changes nothing — and --dry-run shows the full plan before anything is written.

Every member has one of three roles. Viewers get read-only access, editors can change specs and agent setups, and owners can also invite, re-role and remove members. You invite people by email — there's no separate accept step, and they get access the first time they log in.

No. Mind-map, decompose, implement is a starting point, not a mandate. The /athenode-init skill looks through your repository and recommends settings for your gitflow, testing, code review and methodology. Your own rules go in each settings file's Custom section, which later runs never overwrite, and you can clone the default setup and change anything in it.

No. Your code stays in your repository, and your AI tool works on it locally. Athenode stores your specs and agent setups, plus, for each implemented spec, the paths of the files that changed and a short summary of what was done.

Ready to ship better, together?

Spec it. Decompose it. Ship it. All with your AI agent.

Start for free

Join engineers building with Athenode today.