adamrdrew/ushabti

boot-builder

Bootstrap phase context for Builder. Provides current phase, next step, and full phase file contents.

boot-overseer

Bootstrap phase context for Overseer. Provides phase under review with full file contents and card metadata.

approve-phase

Approve a phase — sets status to complete, marks all steps reviewed, updates linked card. Use when declaring a phase green.

create-phase-files

Create a phase directory with all required files in one call. Use instead of separate mkdir + Write calls when creating a new phase.

kick-back-phase

Kick a phase back to building — sets status and adds new step entries to progress.yaml. Use when requesting fixes from Builder.

mark-step-done

Mark a step as implemented in progress.yaml with notes and touched files. Use after completing each step instead of manual Edit calls.

set-phase-status

Set the status field in a phase's progress.yaml. Use instead of manual Edit calls when transitioning phase status.

get-laws-and-style

Get the laws and style for the current project.

phase-status

Query the status of a phase. Returns structured status information for external consumers.

ir-kat

Execute a full Scribe → Builder → Overseer phase cycle. Use when you have a PHASE_PROMPT and want to plan, build, and review a phase end-to-end.

describe-phase-file

Required sections and format for phase.md. Load when defining phase intent, scope, and acceptance criteria.

find-next-phase-number

Determine the next sequential phase ID for creating a new phase. Use when planning a new phase.

check-ushabti-prerequisites

Verify required Ushabti files exist before proceeding. Use when starting agent work to ensure prerequisites are met.

find-current-phase

Find the active phase directory based on status. Use when you need to locate which phase to work on.

find-next-step

Find the next unimplemented step in a phase. Use when determining what to work on next.

get-phase-status

Check the current status of a phase. Use when you need to understand where a phase is in the workflow.

describe-canonical-locations

File locations for laws, style, phases, and docs. Load when locating or creating Ushabti state files.

describe-agent-roles

Agent responsibilities and hard boundaries. Load when determining which agent should act or checking role violations.

describe-docs-system

Documentation system location and maintenance requirements. Load when consulting or updating project documentation.

describe-good-phase

Phase sizing, scope boundaries, and anti-patterns. Load when evaluating whether a phase is well-formed or needs splitting.

describe-laws-and-style

Distinction between laws (invariants) and style (conventions). Load when determining if a constraint is a law or style.

describe-phase-directory-structure

Phase directory layout, naming conventions, and required files. Load when creating or navigating phase directories.

describe-phase-loop

Plan-Build-Review cycle and agent handoffs. Load when transitioning between agents or understanding workflow progression.

describe-progress-file

Structure and field ownership for progress.yaml. Load when reading or updating phase progress state.

describe-questions-policy

Guidelines for asking clarifying questions. Load when deciding whether and how to ask the user for clarification.

describe-required-inputs

Mandatory files agents must read before acting. Load when starting agent work to ensure prerequisites are met.

describe-review-file

Structure and sections for review.md. Load when creating review scaffolds or recording review findings.

describe-steps-file

Step format and ordering rules for steps.md. Load when defining implementation steps or checking step requirements.

describe-ushabti

Core Ushabti concepts and development lifecycle. Load when starting any Ushabti workflow or orienting to the framework.