CynaCons / PowerFlow

One skill for building software with agents.

PRD once. PLAN.md through powerplan. SRS rows before code. Close the loop before "done". Workers through PowerSpawn. Written once, so no project re-specifies it.

GitHub The skill — the method, section by section Decisions D1–D15 powerplan PowerSpawn

The loop

PRD.md (once) ──▶ docs/srs/ rows (before code) ──▶ PLAN.md (powerplan writes it)
                                                             │
     each iteration:  plan/docs ─▶ implement ─▶ verify ─▶ release
                ▲                                           │
                └── new idea → new task · owner report → failing test first ◀┘

  every session:    show_miniplan first · status update last
  every major turn: ends with the miniplan — the console shows the state when you come back
  workers:          PowerSpawn spawns them with the whole brief; the coordinator verifies, commits, then ticks

The ten rules

  1. PRD once. Iterate it with the agent at the start; rewrite only on a declared change of direction.
  2. PLAN.md is the backbone, written only by powerplan: iterations, checkboxes, a smoke task last, a header that cannot go stale.
  3. Miniplan first, last, and at the end of every major turn. The plan is the session's memory; the conversation is not.
  4. Register work before doing it. Tick only with evidence — a test count, a commit, an artifact path.
  5. SRS rows before code. SRS-<FEAT>-NNN, one testable shall per row, never reused.
  6. Close the loop before "done". Tests once, the app launches with a clean console, look at the UI you changed.
  7. Owner reports: quote the owner, failing test first on the reported platform, the owner ticks.
  8. Short AGENTS.md, CLAUDE.md a shim, a memory when you hit a landmine.
  9. Workers get the whole brief — goal + gate, context, allowed paths, done-when, report shape. The coordinator verifies, commits, then ticks.
  10. Release is a checklist, never from an open iteration; check whether CI already picked up the tag before dispatching it.

Two tools

powerplan

The single writer of PLAN.md — an MCP server with a human-language API: show_miniplan, add_tasks, complete_task, close_iteration, check_plan. Tolerant reader, surgical writer, optional [agent: id] tags.

uvx powerplan-mcp · repo

PowerSpawn

Spawn Claude, Codex, Copilot, Grok, Gemini and Mistral workers from one coordinator; every spawn and result logged deterministically to IAC.md. Distribute work across your subscriptions; keep the coordinator's context lean.

Persistent role agents, an ask-coordinator channel and an advisor panel are next. · repo

Install

claude plugin marketplace add CynaCons/PowerFlow
claude plugin install powerflow@powerflow      # user scope: every project, every session
pip install powerplan-mcp                      # the plugin registers powerplan as `python -m powerplan`

Restart Claude Code. In a new directory say "start a new project"; in an existing repo, "audit this repo against PowerFlow". Then the daily verbs: where are we, start the next slice, verify, bug: …, spawn workers for this, release.

What you get in a new project

PRD.md                     skeleton, filled once with you
AGENTS.md · CLAUDE.md      ~40 lines + a shim
docs/srs/README.md         which file owns which requirement tag
docs/agents/memories/      one dated fact per heading
.mcp.json                  powerplan
PLAN.md                    created through powerplan — v0.1.0 with its smoke task, never copied