shinzui

Help author, validate, and edit mori/cookbook.dhall cookbook extension catalogs. Covers entry fields, content types, topics, imports, and validation rules. TRIGGER when: user wants to create, edit, or validate their mori/cookbook.dhall config.

Bootstrap a complete corpus project from a repo name — initializes git, adds upstream subtrees, writes mori.dhall and Justfile, validates, registers, and optionally sets up cookbook and documentation entries. TRIGGER when: user wants to create a corpus project, wrap upstream repos as subtrees, or set up a third-party code reading workspace.

Help author, validate, and edit mori.dhall project configuration files. Covers project identity, packages, dependencies, repositories, documentation, skills, and subagents. TRIGGER when: user wants to create, edit, or understand their mori.dhall config.

Create, implement, discuss, or update execution plans (ExecPlans) — self-contained design documents that guide a coding agent or novice through delivering a working feature or system change. Use when planning significant work, implementing from a plan, or recording design decisions. TRIGGER when: user wants to plan a feature, follow a plan, or manage ExecPlan documents.

Create and manage master plans that decompose large initiatives into multiple coordinated ExecPlans with dependencies and integration points. TRIGGER when: user wants to plan a large initiative, coordinate multiple exec-plans, or track multi-plan progress.

Create a new Bun/TypeScript derivation using bun2nix from a GitHub URL. Use when the user wants to package a JavaScript/TypeScript npm package as a Nix derivation.

Create, implement, discuss, or update execution plans (ExecPlans) — self-contained design documents that guide a coding agent or novice through delivering a working feature or system change. Use when planning significant work, implementing from a plan, or recording design decisions. TRIGGER when: user wants to plan a feature, follow a plan, or manage ExecPlan documents.

Create a new Rust derivation from a GitHub URL. Use when the user wants to add a new Rust package to their nix derivations.

Create, implement, discuss, or update execution plans (ExecPlans) — self-contained design documents that guide a coding agent or novice through delivering a working feature or system change. Use when planning significant work, implementing from a plan, or recording design decisions. TRIGGER when: user wants to plan a feature, follow a plan, or manage ExecPlan documents.

Create, implement, discuss, or update execution plans (ExecPlans) — self-contained design documents that guide a coding agent or novice through delivering a working feature or system change. Use when planning significant work, implementing from a plan, or recording design decisions. TRIGGER when: user wants to plan a feature, follow a plan, or manage ExecPlan documents.

Create and manage master plans that decompose large initiatives into multiple coordinated ExecPlans with dependencies and integration points. TRIGGER when: user wants to plan a large initiative, coordinate multiple exec-plans, or track multi-plan progress.

Generate or refresh a human-readable README.md for a Seihou blueprint, documenting its version, variables, prompts, baseline modules, reference files, allowed tools, tags, and how the agent run produces output — so readers understand the blueprint without reading blueprint.dhall or prompt.md. Use when authoring or updating documentation for a blueprint.

Produce a standardized JSON digest of a MasterPlan (or, explicitly, all of them). Parses the Exec-Plan Registry, computes the dependency graph (ready / blocked / critical path / parallel frontier), embeds per-child ExecPlan digests, cross-references git commit trailers (MasterPlan: and ExecPlan:), and surfaces coordination issues a human would miss when skimming — registry drift, missing back-references, cascade gaps, integration-point violations, blocked critical paths. Emits a single JSON envelope.

Produce a standardized JSON digest of an ExecPlan (or, explicitly, all of them). Extracts status, progress, discoveries, decisions, and outcomes, cross-references git commit trailers, and surfaces issues a human skimming the plan would miss (stale active plans, orphaned discoveries, missing sections, contradictions). Emits a single JSON envelope suitable for dashboards, agent hand-offs, and automated reporting.

Release the keiro Hackage packages (keiro-core, keiro, keiro-pgmq, keiro-migrations, keiro-dsl) together under one shared PVP version, in dependency order.

Create, implement, discuss, or update execution plans (ExecPlans) — self-contained design documents that guide a coding agent or novice through delivering a working feature or system change. Use when planning significant work, implementing from a plan, or recording design decisions. TRIGGER when: user wants to plan a feature, follow a plan, or manage ExecPlan documents.

Create and manage master plans that decompose large initiatives into multiple coordinated ExecPlans with dependencies and integration points. TRIGGER when: user wants to plan a large initiative, coordinate multiple exec-plans, or track multi-plan progress.

Author a keiro service as a typed `.keiro` specification and drive the keiro-dsl toolchain end to end: write the spec, `check` it, `scaffold` the symbol-free deterministic layer plus typed holes, fill the holes and the transducer body against the GENERATED signatures, run the harness, and `diff` the spec to gate unsafe evolution. TRIGGER when: building or changing a keiro service (aggregate/snapshot, process manager + timer, router, Kafka inbox/outbox/contract, pgmq workqueue/dispatch, read model, durable workflow/operation) and you want the spec to be the source of truth.

Release all packages to Hackage following PVP

Create, implement, discuss, or update execution plans (ExecPlans) — self-contained design documents that guide a coding agent or novice through delivering a working feature or system change. Use when planning significant work, implementing from a plan, or recording design decisions. TRIGGER when: user wants to plan a feature, follow a plan, or manage ExecPlan documents.

Create and manage master plans that decompose large initiatives into multiple coordinated ExecPlans with dependencies and integration points. TRIGGER when: user wants to plan a large initiative, coordinate multiple exec-plans, or track multi-plan progress.

Create and manage master plans that decompose large initiatives into multiple coordinated ExecPlans with dependencies and integration points. TRIGGER when: user wants to plan a large initiative, coordinate multiple exec-plans, or track multi-plan progress.

Create, implement, discuss, or update execution plans (ExecPlans) — self-contained design documents that guide a coding agent or novice through delivering a working feature or system change. Use when planning significant work, implementing from a plan, or recording design decisions. TRIGGER when: user wants to plan a feature, follow a plan, or manage ExecPlan documents.

Release keiki and its sibling packages to Hackage following the Haskell PVP. Bumps versions, updates changelogs, runs the project's check gates, and publishes keiki, keiki-codec-json, and keiki-codec-json-test in dependency order.

Release the openapi-hs package to Hackage following PVP

Release all kioku packages to Hackage following PVP

Cut a release of the shikumi Haskell packages and publish them to Hackage following the Haskell PVP (A.B.C.D). Inspects changes since each package's last tag, computes the version bump, updates cabal versions, internal dependency bounds, and changelogs, runs the project's format/build/test/check gates, commits, tags, pushes, publishes to Hackage in dependency order, and creates per-package GitHub releases. Use when preparing a Hackage release.

Release all packages to Hackage following PVP

Release shibuya-pgmq-adapter to Hackage following PVP, coordinating with shibuya-core releases