القائمة
Use when determining MVP readiness status across domains, identifying blockers preventing completion, assessing domain maturity levels, or prioritizing next work targets
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Routes agents to the correct Despaghettify task markdown — check vs solve vs add-task vs autonomous loop vs clean vs reset. Triggers on despaghettify orchestration, spaghetti pipeline, M7 scan then implement, run spaghetti-autonomous-agent-task, which DS next, wipe artefacts only or full hub reset.
Routes agents to the Contractify audit track — discovery, drift, conflicts, actionable JSON. Triggers on contract audit, contractify check, run contractify audit, repository contract drift.
Use when verifying gate health after merges, diagnosing gate failures, troubleshooting false positives, adjusting thresholds, or syncing enforcement config with baseline updates
Use when running comprehensive governance health checks, detecting cross-suite drift, verifying coherence before major merges, or synthesizing findings across contractify, docify, and despaghettify audits
Routes agents to the correct Despaghettify task markdown — check vs solve vs add-task vs autonomous loop vs clean vs reset. Triggers on despaghettify orchestration, spaghetti pipeline, M7 scan then implement, run spaghetti-autonomous-agent-task, which DS next, wipe artefacts only or full hub reset.
Use when integrating YAML content authority (God of Carnage builtin roles) into turn execution, testing authority conflict detection, verifying YAML module loads correctly, or ensuring content authority flows through turn graph
| name | mvp-readiness-assessment |
| description | Use when determining MVP readiness status across domains, identifying blockers preventing completion, assessing domain maturity levels, or prioritizing next work targets |
Rapidly assess current MVP state against audit criteria and identify blockers. Provides structured readiness scoring, domain maturity analysis, and prioritized next-target recommendations based on leverage and impact.
Trigger when:
When NOT to use:
git status to identify recent changespython run_tests.py --suite all'fy'-suites/ directories for audit reportsAssess 6 critical domains (score: 0% = not started, 50% = partial, 100% = complete):
| Domain | Meaning | Status Check |
|---|---|---|
| Runtime Authority | Turn execution framework complete, seams verified | Check turn_graph.py, validation logic, commit effects |
| Validation Rules | GoC validation engine formalized and testable | Check GATE_SCORING_POLICY_GOC.md, rule specifications |
| Commit Effects | State transitions apply correctly, persistence works | Check world_state.py updates, database migrations |
| Evidence Visibility | Render/visibility pipeline complete and correct | Check render functions, observer pattern implementation |
| Continuity | Turn carry-forward logic correct, no state drift | Check state initialization, reset functions |
| Governance | Gates passing, baselines current, enforcement working | Check fy_governance_enforcement.yaml, audit reports |
For each domain scoring <100%, document:
Current score: (domain1% + domain2% + ... + domain6%) / 6
Target: 100% across all domains
Gap analysis: 100% - current_score = work_remaining
Identify 3 candidate targets:
Recommend best based on: leverage + confidence + time available
Markdown report with:
Scenario: Ready to assess MVP before phase transition
User: "Is MVP ready for stakeholder review?"
You:
| Mistake | Fix |
|---|---|
| Scoring without checking code (opinion-based) | Always inspect: tests, audit reports, source files |
| Confusing "complete" with "perfect" | 100% means minimum viable, not fully optimized |
| Ignoring hard blocker dependencies | Check which domains other domains depend on |
| Picking next target by interest not leverage | Use leverage matrix to prioritize impact |
| Not documenting blocker evidence | Always capture "what prevents this" with specifics |
Saves 2-3 hours of stakeholder/team sync time per readiness check. Moves MVP decisions from ambiguous ("is it ready?") to data-driven ("here's the gap"). Enables prioritization by actual impact, not noise.