القائمة
This skill should be used when the task changes phase, new files are touched, a gate result changes, or a blocker appears. Keeps workflow state current across phases.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | state-sync |
| description | This skill should be used when the task changes phase, new files are touched, a gate result changes, or a blocker appears. Keeps workflow state current across phases. |
Use this skill whenever task state changes.
Reference:
Update the state file whenever any of these change:
discovery-complete or planning-done; keep phase to the six canonical values onlyrequirements.openQuestions or delivery notes instead of hiding itneeds-clarificationclarifiedapprovednot-startedin-progresscompletedproposedpassedfailednot-applicableblockedready-for-reviewAccurate state is what makes strict hooks and deterministic recovery possible.
Exact enum reminders:
phase: discovery, planning, implementation, quality-gates, verification, deliveryrequirements.status: needs-clarification, clarified, approvedplan.status: not-started, proposed, approved, blockedimplementation.status: not-started, in-progress, completed, blockeddelivery.status: blocked, ready-for-review, approvedWhen a terminal is available, prefer the built-in state API over ad hoc manual edits:
printf '%s' '{"phase":"planning","requirements":{"status":"approved"}}' | \
node --experimental-strip-types --no-warnings bin/vibe task workflow:hook -- update-state
Or use shorthand CLI arguments when that is easier in the current host:
node --experimental-strip-types --no-warnings bin/vibe task workflow:hook -- update-state \
phase=implementation \
implementation.status=in-progress
This keeps version, lastUpdated, schema validation, and transition validation consistent.
This skill should be used when implementing code, creating files, or writing new features. Provides complete file structure, naming patterns, and import rules.
Decompose large requirements into phased task files that fit AI context windows using Gherkin + State Machine approach.
This skill should be used when working with database, Drizzle ORM, entities, schemas, migrations, and seeds. It provides Rails-style DB conventions, local sqlite/libSQL file defaults, and Effect-friendly data patterns.
Use this skill when generating enterprise admin, back-office, or operations module UI. Activates on: new module screen, admin panel, dashboard, operations list, approval queue, entity detail, multi-step form wizard, RBAC console, audit log, analytics cockpit, support console, settings page, or any layout described as "enterprise", "compact", or "admin-heavy". Provides recipe selection, page anatomy contract, density mode, state checklist, and AI prompt template.
This skill should be used when performing browser testing, verifying in browser, or runtime checks. Guides browser verification patterns.
This skill should be used when working with Chakra UI, UI components, or the design system. Guides Chakra UI v3 and Ark UI patterns.