القائمة
Prove a change works end-to-end by driving the real flow — the dynamic counterpart to hima-verdict's static review.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Bootstrap a new project or catch up an agent on an existing one in minutes by reading vision/goals/state and scaffolding the minimum brain files.
Produce the structural plan — component boundaries, contracts, data flow — plus a lightweight decision record, from a sealed charter.
Formalize intent into a spec artifact (Gherkin scenarios, acceptance criteria, criticality tags) before any non-md file may change.
Declare and audit the per-project disciplines (cadence, branching, testing, architecture, methodology) that the pluggable StageSkillMap resolves against.
Implement the minimum code to satisfy the charter's RED tests, one logical change per commit.
Cited, multi-source research pass for H/C decisions or true blockers — converts findings into requirements, risks, and rejected alternatives.
| name | hima-warden |
| description | Prove a change works end-to-end by driving the real flow — the dynamic counterpart to hima-verdict's static review. |
| stage | meta |
| source | base |
| mode | force |
Exercise the actual runtime surface a change touches instead of trusting tests, a diff read, or a code review alone. hima-warden is the dynamic proof step: it drives the affected flow (UI, API, CLI) and observes real behavior before a completion claim is trusted.
The affected flow has been driven for real with recorded evidence, and the observed behavior matches (or explicitly deviates from, with a named gap) the charter's acceptance criteria.
