claude

ushabti

File-backed, agent-driven development system with specialized agents for planning, building, and reviewing Phases

6 on GitHubby Adam Drewv1.9.6GPL-3.0-or-laterupdated 8 months ago

Not in a marketplace yet, so it loads for one session with --plugin-dir.

Plugin ushabti in adamrdrew/ushabti. Commands read from the repo's manifest — 1 month ago.

What it installs

Skills (33)

  • approve-phase

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

  • 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.

  • check-ushabti-prerequisites

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

  • complete-card
  • create-card
  • 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.

  • describe-agent-roles

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

  • describe-canonical-locations

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

  • describe-cards
  • 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-file

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

  • 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.

  • find-current-phase

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

  • find-next-phase-number

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

  • find-next-step

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

  • get-laws-and-style

    Get the laws and style for the current project.

  • get-phase-status

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

  • 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.

  • 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.

  • list-cards
  • 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.

  • phase-status

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

  • set-phase-status

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

Subagents (7)

  • artisan

    Define code conventions, patterns, and style guide. Use when establishing how things should be built, naming conventions, or architectural preferences.

  • builder

    Implement planned phases step by step. Use when writing code, executing implementation plans, or building features defined by Scribe.

  • lawgiver

    Define project invariants, constraints, and non-negotiable rules. Use when establishing laws, setting boundaries, or capturing what must never change.

  • overseer

    Review and approve completed phases. Use when verifying implementation, checking acceptance criteria, or declaring phases complete.

  • scribe

    Plan development phases with steps and acceptance criteria. Use when starting new work, breaking down features, or creating implementation plans.

  • surveyor

    Document an existing codebase for Ushabti onboarding. Use when starting with an existing project, creating system documentation, or mapping code architecture.

  • vizier

    Conversational advisory agent. Use when you need guidance, want to evaluate options, identify risks, or understand codebase patterns. Cannot modify code or files.

View source on GitHub

Similar plugins

Matt Pocock's agent skills for real engineering (grilling, spec/ticket flows, TDD, code review, domain modelling and more).

39 skills

mattpocock/skills 323,108

superpowers

claudecodex

Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques

15 skills · hooks

obra/superpowers 316,836

claude-mem

claudecodex

Persistent memory for Claude Code: the next session starts where the last one left off.

29 skills · 1 MCP server · hooks

thedotmack/claude-mem 116,618

mem0

claudecodex

Cross-session memory and token savings for coding agents.

6 skills · 1 agent · 1 MCP server · hooks

mem0ai/mem0 68,893

diagram-design

claudecodex

Editorial diagrams in your brand, as self-contained HTML and SVG. Architecture, flowcharts, sequence, state machines, ER and database schemas, timelines, swimlanes, org charts, Gantt, Wardley maps, user journeys, service blueprints, UML class, lifecycle phase maps, and charts from bar, line and scatter to Sankey, treemap and heatmap, plus many more. Redraws draw.io, Mermaid, Excalidraw and PlantUML files. Exports SVG and PNG.

1 skill · 7 commands

cathrynlavery/diagram-design 66,757

context7

claudecodex

Up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your coding agent's context.

1 MCP server

upstash/context7 64,709

Maintain ushabti?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex pluginslisted