القائمة
Verify required Ushabti files exist before proceeding. Use when starting agent work to ensure prerequisites are met.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | check-ushabti-prerequisites |
| description | Verify required Ushabti files exist before proceeding. Use when starting agent work to ensure prerequisites are met. |
| user-invocable | false |
Run these commands to verify required files exist:
[ -f .ushabti/laws.md ] && echo "✓ laws.md exists" || echo "✗ laws.md MISSING (run Lawgiver)"
[ -f .ushabti/style.md ] && echo "✓ style.md exists" || echo "✗ style.md MISSING (run Artisan)"
[ -f .ushabti/docs/index.md ] && echo "✓ docs/index.md exists" || echo "✗ docs/index.md MISSING (run Surveyor)"
[ -d .ushabti/phases ] && echo "✓ phases/ exists" || echo "✗ phases/ MISSING (run Scribe)"
| Agent | laws.md | style.md | docs/ | phases/ |
|---|---|---|---|---|
| Lawgiver | Creates | — | Creates scaffold | — |
| Artisan | Required | Creates | — | — |
| Surveyor | — | — | Creates comprehensive | — |
| Scribe | Required | Required | Required (scaffold OK) | Creates |
| Builder | Required | Required | Recommended | Required |
| Overseer | Required | Required | Recommended | Required |
For a new project (empty directory):
.ushabti/laws.md and a minimal docs scaffold (.ushabti/docs/index.md).ushabti/style.md, recommends Surveyor for comprehensive docs.ushabti/docs/For an existing project:
Scaffold (created by Lawgiver): Minimal index.md with placeholder content. Marked with "Scaffold documentation" text. Sufficient for Scribe to plan, but Surveyor should run for full documentation.
Comprehensive (created by Surveyor): Full project documentation with multiple files covering architecture, systems, and APIs.
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.