القائمة
Quick summary of current project state (latest session + Unreleased + key rules)
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Domain Engineering diagnostic — shows what the classifier decides for an objective (CMIS/DAS/profile/skills/mode). Observation-only; never mutates or blocks.
Business-driven methodology entry point — classify (intake), create/advance an Operation or Business work context, and drive the intake → operation → nested-workflow flow. Host-neutral; dry-run by default.
Workflow Navigator — shows the current phase, deliverables, and next commands for an ADR-0057 workflow. Read-only; never mutates state.
Start a focused session on one objective — locks scope, blocks opportunistic refactors.
Deterministic QA gate (ADR-0055) — run the project suite; green + complete acceptance criteria ⇒ qa-approve testing cards into conclusion; red ⇒ report (and qa-reject only attributable failures).
L6 — autonomous feature pipeline. Drives the full squad: design → implement → review → test → log. Checkpoints can be manual or automatic.
| name | source-command-state |
| description | Quick summary of current project state (latest session + Unreleased + key rules) |
Use this skill when the user asks to run the migrated source command state.
⚠️ Deprecated (1.0): prefer /audit for a fuller, prioritized health view. This quick state read still works for now.
Summarize the current state of this project in at most 12 lines. To do so:
Run node contextkit/tools/scripts/context-pack.mjs [ADR-0027] — one bounded
bundle with the latest-session digest, [Unreleased], the immutable rules, the
open backlog, and recent ADRs. Reason over the pack instead of opening those
files separately; open a full file only if the pack flags something to inspect.
(Level ≥ 7 only — fleet capability, ADR-0097) Optionally add a one-line
Fleet/Agents read by running node contextkit/tools/scripts/fleet-compliance.mjs
and node contextkit/tools/scripts/agent-registry.mjs (both --json, advisory,
read-only, fail-open). Surface just the headline — fleet repos scanned + weakest
compliance, and agent count + agents without a briefing. Omit the line entirely
when the fleet registry is empty or the data is unavailable (never invent).
Structure the answer in 3 blocks:
[Unreleased] and the current phase.Do not invent — only cite what is in the files. If something is empty, say "empty".