ushabti

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

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

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

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

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

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

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

Get the laws and style for the current project.

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

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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