# Atona

> Shape and maintain a useful initiative plan from the current goal, decisions, dependencies, and evidence. Use for material work that needs a coherent route to an outcome, including changed plans and coordinated delivery. Use formal lifecycle gates only when the initiative requires them.

- Skill: `quantipixels/atona` (Agent Skill, multi-file: 10 files)
- Install (CLI): `npx skillmds@latest add quantipixels/atona`
- Raw SKILL.md: https://api.skillmd.com/api/skills/quantipixels/atona/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: quantipixels (https://skillmd.com/u/quantipixels)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/quantipixels/atona

---


# Atọ́nà

Keep one current plan that makes the desired outcome, remaining choices, dependencies, and next action clear.

Delegate substantial analysis, research, and expert work to subagents, returning concise findings and evidence links to keep the main context lean.

## Shape the plan

Start from supplied decisions and current evidence. Do not replay discovery or ask the user for facts you can establish. Distinguish confirmed requirements from inference, and keep the scope and non-goals explicit.

When project knowledge could change the approach, constraints, sequence, or proof, reuse applicable evidence already supplied; otherwise search the existing knowledge and research destinations by affected concepts and components. Read plausible matches, check their authority and current applicability, and carry forward only what changes this plan. Flag conflicts rather than treating historical guidance as current authority. An empty search does not itself require a new record or a repository-wide search.

Include the outcome and observable acceptance, the material decisions and assumptions, a useful delivery sequence, dependencies and risks that can change it, the current blocker, and the next action. Match detail to what a fresh contributor would otherwise have to invent. Omit empty sections and bookkeeping that has no consumer.

Use `arojinle`, `amose`, `seda-spec`, `architect`, and `seda-ticket` as needed.

When the initiative cannot yet be responsibly stated at full depth, read [progressive shaping](references/progressive-shaping.md). Resolve prerequisites without inventing future requirements or blocking independent work.

## Challenge readiness

Before presenting an initiative plan as ready to execute, run a [premortem](references/premortem.md) against the current plan. Reconcile material findings into the plan before declaring readiness; formal lifecycle work must pass this gate before `Planned`. Keep the analysis proportional and in the existing plan or conversation, not a separate report.

## Keep it current

After a material decision, discovery, or delivery result, update the affected plan. Reopen only dependent choices and invalidate only proof that no longer applies. A partly superseded plan is not wholly current.

Use the delivery owner's actual evidence. A task count, worker completion, provider status, or aggregate score does not prove the accepted outcome. Keep missing proof, blocked dependencies, changed scope, and residual limits visible. Planning advice does not authorize implementation or publication.

When the governing workflow requires named readiness states, coordinated multi-candidate delivery, or a durable lifecycle record, use [managed initiatives](references/managed-initiative.md). That branch retains the formal planning, contract, delivery, and closure gates; an ordinary plan does not acquire them by being large or involving several skills.

## Deliver

Keep one-session plans in the conversation. Update the existing project source when persistence is needed; use `akosile` for a selected shared workspace.

Use `html-artifact` as needed, with [the initiative brief](references/human-view.md).

Keep ordinary rationale in the plan and normal delivery history. Use [durable reconciliation](references/durable-reconciliation.md) only for a real governing-knowledge obligation. Required stale sources or missing authority remain blockers, not reasons to manufacture a reconciliation ledger.

Return the current plan, any blocking choice or evidence gap, and the first useful action. Report completion only when the accepted outcome and its required proof are satisfied; keep implementation, integration, and release state distinct.