asimov-plugin

Plugin asimov-plugin from marketplace asimov-marketplace in context-and-oss/asimov. Commands read from the repo's manifest — yesterday.

Skills (27)

• artifact-d101-authoring

  How to write or change a D101 feature-design file (documentation/features/D101-*.html and its mockups under documentation/features/mockups/d101-*/) so it still meets the D101 contract — the definition's bars and the HTML template's structure. Use whenever you create, render, edit, or fix any part of

• artifact-d101-gap-review

  The gap review of a D101 feature design — walk every section against the HTML template and the definition's quality rules, then run the checks of the bar the document's phase calls for (§8a business-complete while §6 is open, §8b gap-free once written), and report findings in two tables with no verd

• artifact-persona-authoring

  Author a custom persona review skill for the product repo — interview the author for the five persona fields (identity, knows cold, does not know, has, is reviewing to), check the reader against the persona-review quality bar, then render the persona template into a self-contained SKILL.md at .claud

• artifact-risk-log-authoring

  The only writer of the risk log, project/risk-log.html — turn what a person said about the engagement's risks into one change file (register, change, decide a state, hand over, review, opt out, repair), in the project's language, with the reason and decider the state needs, and hand it to the risk-l

• artifact-risk-log-view

  Print the risk log, project/risk-log.html, as the fixed 80-column view the weekly review reads top-down — the register's date and counts, then every open risk in full by state and score, the resolved ones as a count, or the opt-out where no register is kept. Use inside asimov-project to show the reg

• artifact-s101-authoring

  How to cut one design that meets contracts/design.md, a D101 at Full design or a normalised design cache, into one S101 implementation plan (specs/<slug>/S101-<slug>.md) — the plan part of a specification under contracts/specification.md: slices from the acceptance criteria, a Foundation phase 0 onl

• artifact-s101-ledger

  Read and write the run state of one build — the ledger specs/<slug>/S101-<slug>.ledger.md beside a ready S101 — so a run can start, record every attempt, report and ruling, resume where it stopped, and refuse when the plan changed. Use inside asimov-build for every ledger operation (start, position,

• artifact-s101-validation

  Validate an S101 implementation plan against its bar, dispatch-ready, in one of two modes — graph-only on the S101 alone (frontmatter parses as the phase tree, no cycle, tester before builder in every slice, every slice task after the Foundation where the plan has one, contracts table consistent, co

• artifact-s101-view

  Render one S101 implementation plan (specs/<slug>/S101-<slug>.md) as the fixed plan view a person reads in chat — the phase tree with what each phase delivers, its checkpoint and one line per task, the coverage line, the assumptions line, the design gaps — in the language of the conversation. Use wh

• artifact-s102-authoring

  How to write one S102 task spec (specs/<slug>/S102-<slug>-NNN-<task>.md) for one builder role from one task line in an S101 tree — the task part of a specification under contracts/specification.md: header copied from the task line plus the owned files and the contract names it consumes and produces,

• artifact-s102-validation

  Validate one S102 task spec against its shape, the way a JSON file is checked against its schema — header keys present and equal to the task line in the S101 tree, owned paths that exist or are created upstream, consumed names in a plan row, declared at their path or in a referenced package, no plac

• asimov-build

  Build one ready plan — specs/<slug>/S101-<slug>.md with its validated task specs — phase by phase, where each task goes to the Asimov agent its role names, fresh at its first attempt and continued by message after, with its task spec as the only brief; once a phase is built Baley reviews its diff ag

• asimov-design-review

  Review one D101 under documentation/features/ without changing it — resolve the phase it stands in, offer the reviews that phase calls for (the gap review against §8a or §8b, the business-persona reads of §2/§4, the technical-persona reads of §4 and §6) and run the ones the author picks, each delega

• asimov-design

  Design one feature as a D101 under documentation/features/ — interview the author through requirements and the business design, write the file with the technical design declared open and stop; in a later run, against that file, write the technical design and flip it to Full design. Also renders a le

• asimov-project

  The Project frame's one entry point — the engagement the stages run inside. Takes the artifact and the action from the words of the message that names it (the risk log first; a closure report and the project setup later), composes that artifact's authoring and view skills, and writes one page per ar

• asimov-spec

  Turn one design, a D101 at Full design or an approved Jira ticket, into its implementation plan (S101) and task specs (S102s) under specs/<slug>/ — read the design and the repo, ask at most five questions with defaults, cut and check the plan in one writer subagent that stays alive for the whole run

• codex-asimov-init

  Bootstrap a product repo to use the Asimov toolkit from Codex — writes the Asimov context into an AGENTS.md managed region, delivers the Codex subagent shells to .codex/agents/, scaffolds detected-stack convention read-lists, and generates the documentation/ landing site. Read-only on every other fi

• persona-athena

  Review a document as Athena — a pragmatic architect who has shipped systems like this one and reads the design, including the technical section, for whether the approach is sound and buildable. Use before committing to a design, to catch the assumptions the business quietly lays on the technology. T

• persona-hermes

  Review a document as Hermes — a budget-minded sponsor who decides where the money goes and asks whether the value justifies the spend. Use before taking a design or proposal to sign-off, to find the scope that isn't paid for by its return. Triggers on "review as Hermes", "read this as Hermes", "is t

• persona-poseidon

  Review a document as Poseidon — a frontline operator who runs the work every day, knows how it really happens and where it breaks, and has never opened the codebase. Use before taking a design, analysis, or proposal to sign-off, to find where it describes a tidy process no one actually follows. Trig

• pm-advisor

  Advises on the Delivery Model — the four fixed phases (Proposal, Scoping, Development, Operations), the approach catalogue (Scrum, Kanban, use-case delivery, prototyping, launch/hyper care), the discipline catalogue and the selection guide. Use when choosing how to run an engagement, picking an appr

• role-angular-builder

  The Angular builder method — write or modify frontend TypeScript/Angular code so it conforms to the active product repo's own Angular conventions, read at run-time from documentation/conventions/angular/README.md, never a generic default. Use for frontend implementation work that must match house st

• role-code-reviewer

  The code-reviewer method — review the current branch's diff against its base, or a named set of files against the task specs they were built from (review vs. spec, inside asimov-build), for conformance to the active product repo's own conventions (read at run-time from documentation/conventions/<sta

• role-dotnet-builder

  The .NET builder method — write or modify production C#/.NET backend code so it conforms to the active product repo's own .NET conventions, read at run-time from documentation/conventions/dotnet/README.md, never a generic default. Use for backend implementation work that must match house style — nam

• role-dotnet-tester

  The .NET tester method — author unit tests for production code touched by the current branch so they conform to the active product repo's own test conventions, read at run-time from documentation/conventions/test/README.md, never a generic default. Use to add or extend .NET test coverage in house st

• role-s102-verifier

  The verifier method, the Test stage's "agent vs. spec" — run every done-when of a phase's task specs (specs/<slug>/S102-*.md) and the phase's checkpoint exactly as written, change nothing, and report per task pass or fail with the command and its last line. Use when a phase has been built and review

• tool-deck-authoring

  How to write a slide deck as one self-contained HTML file from the plugin's deck resource (resources/deck/) — presented in a browser, speaker notes under N, a PDF under Ctrl+P, styled by one theme file. Use whenever someone asks for a presentation, a deck, slides, a pitch, a talk, a session, a brief

Slash commands (1)

• /asimov-plugin:asimov-init

  Bootstrap a product repo to use the Asimov toolkit — writes an Asimov-owned asimov.md and wires it into CLAUDE.md via an @-import, scaffolds detected-stack convention read-lists, and generates the documentation/ landing site. Read-only on every other file. Supersedes /docs-init.

Subagents (5)

• baley-the-code-reviewer

  Reviews a changeset (diff against the base branch) against the active product repo's own conventions plus correctness and safety, and emits a structured pass/flag/fail finding report. Read-only — it reports findings, never edits code and never declares an approval verdict. Use for an automated first

• calvin-the-test-author

  Authors tests for existing code so they conform to the active product repo's test conventions (.NET unit tests for now). Use to add or extend test coverage in house style — test naming, arrange-act-assert, coverage thinking. Reads the repo's conventions at run-time, flags gaps or conflicts, and flag

• daneel-the-angular-developer

  Writes or modifies frontend TypeScript/Angular code so it conforms to the active product repo's Angular conventions. Use for frontend implementation work that must match house style — component structure, naming, RxJS idioms. Reads the repo's conventions at run-time and flags gaps or conflicts inste

• giskard-the-dotnet-developer

  Writes or modifies production C#/.NET backend code so it conforms to the active product repo's .NET conventions. Use for backend implementation work that must match house style — naming, layering, service patterns. Reads the repo's conventions at run-time and flags gaps or conflicts instead of guess

• powell-the-verifier

  Verifies a built phase against its task specs — runs every done-when and the phase's checkpoint exactly as written and reports pass or fail per check with the command and its last line. Read-only on the code; the shell is only for running the checks. Use after a phase is built and reviewed, before t

Hooks (6)

• SessionStart

  pwsh -NoProfile -File "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/asimov-log.ps1" || powershell -NoProfile -ExecutionPolicy Bypass -File "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/asimov-log.ps1"; exit 0

• UserPromptExpansion

  pwsh -NoProfile -File "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/asimov-log.ps1" || powershell -NoProfile -ExecutionPolicy Bypass -File "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/asimov-log.ps1"; exit 0

• PreToolUse

  pwsh -NoProfile -File "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/asimov-log.ps1" || powershell -NoProfile -ExecutionPolicy Bypass -File "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/asimov-log.ps1"; exit 0

• SubagentStart

  pwsh -NoProfile -File "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/asimov-log.ps1" || powershell -NoProfile -ExecutionPolicy Bypass -File "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/asimov-log.ps1"; exit 0

• SubagentStop

  pwsh -NoProfile -File "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/asimov-log.ps1" || powershell -NoProfile -ExecutionPolicy Bypass -File "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/asimov-log.ps1"; exit 0

• SessionEnd

  pwsh -NoProfile -File "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/asimov-log.ps1" || powershell -NoProfile -ExecutionPolicy Bypass -File "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/asimov-log.ps1"; exit 0

Similar plugins