← ClaudeAtlas

kinglisted

Use when a user invokes /king, asks to initialize or scaffold a Work or ZCode project, or asks to rescue, understand, repair, refactor, or productionize an existing project. Provides a safe NEW/RESCUE lifecycle, evidence-based project profiling, solo/team topology selection, plugin policy, approval-gated Create/Merge/Skip/Conflict changes, and truthful verification.
zhangsugang/king-skill · ★ 0 · AI & Automation · score 62
Install: claude install-skill zhangsugang/king-skill
# /king — project initialization and diagnosis Use one approval-gated workflow for greenfield and existing projects. Preserve user work, keep diagnosis read-only, and never commit or push unless the user explicitly asks. ## Classification model Keep the three axes independent: - **Lifecycle — `NEW` or `RESCUE`:** whether King is initializing an effectively empty project or preserving and improving an existing one. - **Domain — `Work` or `ZCode`:** whether the primary deliverable is knowledge work/operations or software/code. - **Topology — `solo` or `team`:** whether one agent works directly or five explicit roles divide the work. `NEW`/`RESCUE` is never a domain. `Work`/`ZCode` is never a lifecycle. `solo`/`team` is never a domain or lifecycle. A profile is the combination of all three axes plus a plugin policy: `minimal`, `balanced`, or `enhanced`. For scoring rules, plugin tables, team roles, question templates, candidate formats, and startup reports, read [`references/PROJECT_PROFILING.md`](references/PROJECT_PROFILING.md) before recommending a profile. ## Interfaces ```text /king <name or goal> # automatic lifecycle and profile recommendation /king --new <name or goal> # force NEW lifecycle /king --rescue <problem> # force RESCUE lifecycle ``` A lifecycle override does not select domain/topology, permit destructive writes, or bypass either confirmation gate. ## Required order Do not reorder or collapse these steps. ### 1. Doctor Run `scripts/pr