Athenode

This is Athenode's own spec-driven development workflow, meant to be used to build Athenode itself.

1. Start a specification with /atn-mindmap: build it up over an iterative Q&A session — you don't need finished content up front, just a starting topic. Each round asks 3-8 questions, saves your answers, and proposes what to explore next until you choose to finish, at which point it synthesizes everything into the final spec. Placement (spec-placement-researcher), codebase feasibility grounding (spec-feasibility-analyst) and dependency research (spec-dependency-researcher) run up front, before the first round of questions. Blocked-by links are set only when a specification is finalized — in the mind map's final step and by spec-decomposition-finalizer — never by spec-decomposer. It can also be used to discuss or think through an existing specification that was already decomposed — one of its decomposed parts — by passing that part's id with --continue.

2. Break it into stages with /atn-decompose: drafts one child "stage" specification per stage, attaches clarifying questions to each, collects your answers, then finalizes every child via spec-decomposition-finalizer, which rewrites each child's content grounded in fresh spec-feasibility-analyst and spec-dependency-researcher findings and sets it to prepared.

3. Implement everything with /atn-apply: fetches the dependency-ordered execution plan for the subtree (prepared and interrupted leaves, following blocked-by links) and, for each one in order, plans it (spec-implementation-planner, backed by spec-feasibility-analyst), implements it (spec-implementer) and has it reviewed when the project's code review settings say (spec-implementation-reviewer), completing intermediate stages as their subtrees finish, before marking the root specification completed.

4. Work through the project's ToDo cards with /atn-todo-dequeue: it offers the open cards one by one, by priority, and per card either starts /atn-mindmap from the card or carries the card out directly without a specification (todo-implementer, reviewed by todo-reviewer), then commits, closes the card and asks how to deliver the commits. With --auto it asks where to work and how to deliver once, at the start, and then carries out every card that needs no answer from the user without a further question. To add a card without leaving the session, use /atn-todo-enqueue: it takes the card's text, asks only for what is missing (type, priority and the open questions you want recorded on it) and records one card.

Two more skills maintain the workflow itself: /atn-settings chooses the project's workflow settings (gitflow, testing, code review, methodology), and /atn-manage lists, creates, changes and deletes plugins and the files, skills, agents, MCP servers and rules of the installed or another plugin, and imports external plugins.