atlas

Plugin atlas from marketplace atlas-os in RangerAndFox/atlas-os. Commands read from the repo's manifest — 1 month ago.

Skills (7)

• atlas-adopt

  Adopt any repository into Atlas governance. Use when setting up Atlas on a new project, or re-running adoption after a toolchain change. Detects the real toolchain from the repo, generates .atlas config, a digest-pinned devcontainer, the validation workflow, CODEOWNERS, and the acceptance-test scaff

• atlas-criterion-critic

  Adversarially attack each acceptance criterion in a mission draft before promotion — try to build an implementation that satisfies the criterion while leaving the outcome false. Use after the mission linter passes and before asking a human to promote a proposal, and whenever amending a criterion.

• atlas-design-review

  Render a UI-bearing change in CI, screenshot the declared screens with chromium, and have the design-director review the actual pixels plus the repo's own end-to-end run. Emits a verdict the design gate enforces. Use on user-facing PRs. The director can block; the owner can override.

• atlas-independent-review

  The independent adversarial review that runs automatically on every PR (via the atlas-review.yml workflow) and gates merge. Produces a plain-language GO / NO-GO a non-technical owner can act on. Use when reviewing a pull request as the required `atlas-independent-review` check, or when running the r

• atlas-mission-linter

  Check a mission draft against the Definition of Ready before it is promoted. Use whenever authoring or amending a mission, and before asking a human to promote a proposal.

• atlas-retrospective

  Close out a mission by generating and interpreting its retrospective. Use after a mission is accepted, abandoned, or superseded — every time, without exception.

• atlas-supervisor

  Run one Atlas mission end-to-end through the roles automatically, stopping only at the two authority gates (promote, merge). Use to drive a mission from a product intent to an opened PR without invoking each role by hand. Session-scoped; holds no authority.

Slash commands (4)

• /atlas:atlas-accept

  Prepare an acceptance decision packet for the human (does not accept — that is a human CLI action)

• /atlas:atlas-adopt

  Adopt this repository into Atlas governance (detects toolchain, generates config, devcontainer, CI, gates)

• /atlas:atlas-mission

  Draft a new mission — Mission Control decides, Mission Author contracts, the critic attacks it, Acceptance Engineer writes the failing tests

• /atlas:atlas-status

  Show the Atlas state of this project — active mission, unproven criteria, gates, invariants

Subagents (8)

• atlas-acceptance-engineer

  Converts an approved mission's acceptance criteria into executable tests that fail before implementation. Use immediately after a mission is approved and BEFORE any implementation planning. Must not see the implementation plan.

• atlas-auditor

  Establishes current reality for a repository or subsystem. Use before planning any mission against unfamiliar or drifted code, and whenever a mission's premise needs verifying. Read-only.

• atlas-design-director

  Independent design and usability advocate. Reviews whether a change LOOKS right and WORKS as intended, from actually-rendered screenshots of the running UI plus the repo's own end-to-end run. Use on user-facing changes. Can block a user-facing PR; the owner can override. Deliberately blind to the im

• atlas-engineering-director

  Owns engineering interpretation, architecture, and execution planning for an approved mission. Use to turn a mission contract into a bounded implementation plan, and to judge integration readiness. Plans and reviews; does not implement.

• atlas-implementer

  Executes one bounded, pre-planned engineering task inside a declared file scope. Use only after the Engineering Director has produced a plan and the Acceptance Engineer has written the tests.

• atlas-mission-author

  Converts an approved product intent into an implementation-neutral mission contract. Use after Mission Control has decided something should happen but before any engineering planning.

• atlas-mission-control

  Owns product direction and acceptance. Use to decide what happens next, to classify and scope work, and to judge whether a completed mission actually achieved its outcome. Drafts mission proposals; never implements.

• atlas-reviewer

  Independent adversarial review of an implementation against a mission. Use after implementation and Director review, when the change touches invariants, security, data, money, or external effects. Deliberately blind to the implementer's account.

Hooks (1)

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/hooks/atlas-guard.mjs"

Similar plugins