adamrdrew
33 verified skills165 total stars
boot-overseer
Bootstrap phase context for Overseer. Provides phase under review with full file contents and card metadata.
data-ai5
skills/create-card
# Create Card Create a new Hieroglyphs-compatible card to track work items, bugs, or features. Cards use the Hieroglyphs format with YAML frontmatter and markdown body, stored in `.ushabti/cards/{slug}/card.md` directories. ## When to Use Create a card when: - Discovering technical debt that should be tracked - Identifying a bug or issue that should be addressed later - Capturing a feature request or improvement idea - Recording any work item that should be tracked separately from the current
development5
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.
documentation5
describe-phase-loop
Plan-Build-Review cycle and agent handoffs. Load when transitioning between agents or understanding workflow progression.
development5
describe-required-inputs
Mandatory files agents must read before acting. Load when starting agent work to ensure prerequisites are met.
data-ai5
describe-steps-file
Step format and ordering rules for steps.md. Load when defining implementation steps or checking step requirements.
development5
get-laws-and-style
Get the laws and style for the current project.
devops5
phase-status
Query the status of a phase. Returns structured status information for external consumers.
development5
describe-good-phase
Phase sizing, scope boundaries, and anti-patterns. Load when evaluating whether a phase is well-formed or needs splitting.
development5
describe-agent-roles
Agent responsibilities and hard boundaries. Load when determining which agent should act or checking role violations.
testing5
describe-canonical-locations
File locations for laws, style, phases, and docs. Load when locating or creating Ushabti state files.
devops5
describe-phase-directory-structure
Phase directory layout, naming conventions, and required files. Load when creating or navigating phase directories.
tools5
describe-progress-file
Structure and field ownership for progress.yaml. Load when reading or updating phase progress state.
data-ai5
describe-review-file
Structure and sections for review.md. Load when creating review scaffolds or recording review findings.
tools5
describe-ushabti
Core Ushabti concepts and development lifecycle. Load when starting any Ushabti workflow or orienting to the framework.
development5
find-next-phase-number
Determine the next sequential phase ID for creating a new phase. Use when planning a new phase.
tools5
find-next-step
Find the next unimplemented step in a phase. Use when determining what to work on next.
tools5
get-phase-status
Check the current status of a phase. Use when you need to understand where a phase is in the workflow.
testing5
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.
data-ai5
check-ushabti-prerequisites
Verify required Ushabti files exist before proceeding. Use when starting agent work to ensure prerequisites are met.
testing5
approve-phase
Approve a phase — sets status to complete, marks all steps reviewed, updates linked card. Use when declaring a phase green.
tools5
boot-builder
Bootstrap phase context for Builder. Provides current phase, next step, and full phase file contents.
development5
skills/complete-card
# Complete Card Mark a card as done by updating its status field to `done` and setting the updated timestamp. This replaces the old ticket archival system where tickets were moved to an `.archived/` directory. ## When to Use Mark a card complete when: - A Phase addressing the card's work has been completed and reviewed - The work item has been fully implemented and verified - The Overseer determines the card's requirements are satisfied ## Status Update Cards track their lifecycle state in
tools5
skills/describe-cards
# Describe Cards Comprehensive documentation of Ushabti's card system—the Hieroglyphs-compatible format for tracking work items, bugs, and features. ## Overview Ushabti uses Hieroglyphs-compatible cards to track work outside the current Phase. Cards replace the previous ticket system, providing alignment with the Hieroglyphs task management tool. Cards are stored as individual directories containing a `card.md` file with YAML frontmatter and markdown body. Unlike the old ticket system (flat
tools5
describe-docs-system
Documentation system location and maintenance requirements. Load when consulting or updating project documentation.
documentation5
describe-laws-and-style
Distinction between laws (invariants) and style (conventions). Load when determining if a constraint is a law or style.
devops5
describe-phase-file
Required sections and format for phase.md. Load when defining phase intent, scope, and acceptance criteria.
development5
describe-questions-policy
Guidelines for asking clarifying questions. Load when deciding whether and how to ask the user for clarification.
testing5
find-current-phase
Find the active phase directory based on status. Use when you need to locate which phase to work on.
tools5
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.
development5
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.
development5
skills/list-cards
# List Cards Scan and list all Hieroglyphs-compatible cards in `.ushabti/cards/`, with optional filtering by status or other criteria. ## When to Use Use this skill when: - You need to see all available work items - Looking for cards in a specific state (e.g., only `todo` cards) - Determining which cards to plan next - Checking card priorities and types ## Card Location Cards are stored in: ``` .ushabti/cards/{slug}/card.md ``` Each card is a directory containing a `card.md` file with YAML
testing5
set-phase-status
Set the status field in a phase's progress.yaml. Use instead of manual Edit calls when transitioning phase status.
data-ai5