zeus

Brainstorm features or run full project planning through structured dialogue. Use --full for initial project-wide planning (includes north star metrics if not set), or --feature <name> for a single feature. Always asks one question at a time. Invokes zeus-plan automatically after spec is approved.

Map an existing (brownfield) codebase into deterministic Zeus artifacts under .zeus/{version}/ so downstream skills can reuse real project context.

Execute all pending tasks in task.json using the zeus-runner.sh shell loop. Tasks are grouped into dependency waves and run with fresh claude CLI subagents. Each task gets an atomic git commit and a mandatory ai-log entry. Supports --version flag for v2/v3/v4 execution.

Initialize a new Zeus project. Creates .zeus/main/ directory structure, sets up config.json with north star metrics, and writes the first evolution.md entry. Use this FIRST before any other zeus skill.

Convert a spec document into structured prd.json user stories and task.json execution units. Called automatically by zeus-brainstorm, but can also be invoked directly. Supports --version flag to target v2/v3/v4 folders.

Display a full status report of the Zeus project — all active versions, task progress, recent feedback attribution, evolution history, and next recommended action.

Create a new version folder (.zeus/v2/, .zeus/v3/ etc.) when user feedback reveals needs that can't be met by the main version. Inherits main config and declares differences. Records everything in evolution.md.

Record user feedback (natural language or structured data), perform AI attribution analysis linking results to past tasks, update evolution.md, and ask the user whether to start a new version. This is the core feedback loop skill.

Generate AI-authored platform test flows (android.test.json, chrome.test.json, ios.test.json) from task.json and prd.json using generate-tests.sh. Can be triggered manually or automatically after zeus-plan. Supports --version flag and --platforms filter.