[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M786Q2B0ZR3G2FPESXJZS2SD":3,"skill-same:01M786Q2B0ZR3G2FPESXJZS2SD":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":14,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M786Q2B0ZR3G2FPESXJZS2SD","sp-explain",null,"Use when the user needs the current stage artifact, project cognition state, or compatibility\u002Fexport atlas artifact explained in plain language without changing the underlying files.","chenziyang110\u002Flaunchdeck","chenziyang110","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F43693913?v=4","01M7863EBWK1D0P6A29YGEMAS4","Robin11","01M7863ECM1VB6RXDMHTW90D2T",0,"MIT","https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fsp-explain\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"sp-explain\"\ndescription: \"Use when the user needs the current stage artifact, project cognition state, or compatibility\u002Fexport atlas artifact explained in plain language without changing the underlying files.\"\ncompatibility: \"Requires spec-kit project structure with .specify\u002F directory\"\nmetadata:\n  author: \"github-spec-kit\"\n  source: \"templates\u002Fcommands\u002Fexplain.md\"\n---\n## Invocation Syntax\n\n- In this integration, invoke workflow skills with `$sp-plan`-style syntax.\n- References such as `\u002Fsp.plan`, `\u002Fsp.tasks`, or `next_command: \u002Fsp.plan` are canonical workflow-state identifiers and handoff values.\n- Preserve those canonical state tokens exactly in artifacts and workflow state; do not rewrite them to this integration's invocation syntax.\n\n\n\n## Workflow Contract Summary\n\n- **When to use**: The user needs to understand the current planning-stage artifact, project cognition state, or compatibility\u002Fexport atlas view before deciding whether to continue, revise, or proceed.\n- **Primary objective**: Translate the current artifact into plain language while staying faithful to what is actually on disk.\n- **Primary outputs**: A structured explanation only; do not rewrite stage artifacts or atlas documents unless another command explicitly requests it.\n- **Default handoff**: $sp-plan or \u002Fsp-tasks only after the user is satisfied with the current understanding and wants to advance.\n- **Execution note**: This summary is routing metadata only. Follow the full contract below end-to-end rather than inferring behavior from the description alone.\n\n## Blocked Exit Contract\n\nIf blocked after safe recovery, read and follow\n`.specify\u002Ftemplates\u002Fworkflow-blocker-template.md` and its JSON schema. Never\nreturn only an error or “ask a human”; preserve state and keep agent-capable\nrepair agent-owned. Set `human_action_required: true` only for authority,\ncredentials, protected systems, human decisions\u002Freviews, or physical access.\nTailor steps, expected results, failure paths, evidence, and resume action to\nCI, visual review, or product decisions. Never claim completion.\n\nFor a feature runtime blocker, do not invent `resume_argv` or overwrite an\nexisting blocker. The CLI returns a read-only `show_argv` and structured\n`resolution_action`; `next_argv` stays empty while evidence is missing. After\nthe criteria are proven, attach sanitized evidence using the action's declared\ninput and execute its base argv. It restores the same owner and keeps the full\nblocker audit.\n\n## User Input\n\n```text\n$ARGUMENTS\n```\n\nYou **MUST** consider the user input before proceeding (if not empty).\n\n## Objective\n\nExplain the current stage artifact in plain language so the user can understand what the system believes, what is settled, what remains open, and what the next stage would do.\n\n## Context\n\n- Primary inputs: the most relevant current stage artifact plus any immediately supporting artifacts needed to explain it accurately.\n- This command is explanation-only. It does not invent state that is absent and does not rewrite the underlying files.\n- If limited collaboration is used for a supporting cross-check, the final explanation still converges back to one render step.\n\n## Process\n\n- Resolve the current stage artifact deterministically.\n- Load only the supporting context needed to explain it faithfully.\n- Optionally run a bounded cross-check lane when the current artifact genuinely benefits from it.\n- Render one final structured explanation in the user's language.\n\n## Output Contract\n\n- Produce a stage-aware explanation with status, risk, and next-step framing.\n- Keep the explanation grounded in what is actually on disk.\n- Be explicit when implementation status or another expected artifact is absent.\n\n## Guardrails\n\n- Do not invent missing state.\n- Do not rewrite stage artifacts from inside `\u002Fsp-explain`.\n- Default to `leader-inline-fallback` only when no safe supporting subagent cross-check lane can be packetized and dispatched safely.\n\n## Project Learning\n\nThe CLI is the only agent-facing Learning read surface:\n\n1. Run `uvx --from git+https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Fspec-kit-plus.git@6fbbf08a0b6833bb783ec6b418d567776b197ae4 specify learning start --command '\u003Cclassic-command-name>' --format json` before deeper non-trivial work.\n2. Select summaries by applicability and triggers; use `uvx --from git+https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Fspec-kit-plus.git@6fbbf08a0b6833bb783ec6b418d567776b197ae4 specify learning list --command '\u003Cclassic-command-name>' --format json` only to filter or page.\n3. Execute one matching card's `show_argv`. Do not parse Learning storage.\n\nAfter minimal live inspection identifies a reused operation or changed entry point, rerun targeted recall with current code, tests, and task\u002Fcontract evidence, for example `uvx --from git+https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Fspec-kit-plus.git@6fbbf08a0b6833bb783ec6b418d567776b197ae4 specify learning list --command '\u003Cclassic-command-name>' --context 'operation_owner=\u003Cowner>' --context 'consumer_owner=\u003Cconsumer>' --context 'outcome=\u003Cresult-family>' --format json`. Do not derive these facets from archived specifications. An exact operation-owner match may surface a cross-command candidate even when the new consumer differs; treat it as a candidate, expand one `show_argv`, verify it against live evidence, and do not auto-apply it.\n\nWhen the entrypoint outcome audit is triggered, persist the live facets as `learning_context`, the contextual invocation as `learning_search_refs`, and returned refs as `learning_candidate_refs`. Record exactly one `applied`, `not_applicable`, or `deferred` item in `learning_dispositions` for every candidate. Do not silently ignore a candidate: applied Learning traces to requirement\u002Fconsequence refs, not-applicable needs current evidence, and deferred needs an explicit deferral ref.\n\n`start`, `list`, and `show` are read-only. Current repository evidence,\n`.specify\u002Fmemory\u002Fconstitution.md`, and explicit user direction override stale or\ncandidate Learning.\n\nAt closeout, corrections, retries, route changes, recovery, false leads, hidden\ndependencies, validation\u002Ftooling\u002Fstate\u002Fcognition gaps, constraints, and near\nmisses are capture signals. Prefer `uvx --from git+https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Fspec-kit-plus.git@6fbbf08a0b6833bb783ec6b418d567776b197ae4 specify learning capture-auto`\nfrom owning state; manual capture includes summary, problem, action, triggers,\nsuccess criteria, avoid items, exceptions, and evidence.\n\n- `fast`: skip unless the task escalates.\n- `accept`, `analyze`, `ask`, `auto`, `constitution`, `explain`,\n  `implement-teams`, `taskstoissues`, and `team`: consume-only; do not violate\n  their write boundaries to capture.\n- Other non-trivial workflows: consume before deeper work; capture reusable\n  signals at closeout or record a no-learning decision.\n\nThe `policy` returned by the CLI is authoritative when prompt wording drifts.\n\n## Mandatory Subagent Execution\n\nAll substantive tasks in ordinary `sp-*` workflows default to and must use subagents.\n\nThe leader orchestrates: route, split tasks, prepare task contracts, dispatch subagents, wait for structured handoffs, integrate results, verify, and update state.\n\nBefore dispatch, every subagent lane needs a task contract with objective, authoritative inputs, allowed read\u002Fwrite scope, forbidden paths, acceptance checks, verification evidence, and structured handoff format.\n\nUse `execution_model: subagent-mandatory`.\nUse `dispatch_shape: one-subagent | parallel-subagents`.\nUse `execution_surface: native-subagents`.\n\n\n## Outline\n\nGoal: Read the current stage artifact, project cognition artifact, or explicitly requested compatibility\u002Fexport atlas artifact and explain it in plain language so the user can understand what the system currently believes, what is decided, what is still open, and what the next phase or next relevant view will do.\n\n1. Run `.specify\u002Fscripts\u002Fpowershell\u002Fcheck-prerequisites.ps1 -Json -PathsOnly` from repo root once (`--json --paths-only` \u002F `-Json -PathsOnly`) and parse the available feature paths.\n   - If `FEATURE_DIR` is not already explicit, prefer `uvx --from git+https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Fspec-kit-plus.git@6fbbf08a0b6833bb783ec6b418d567776b197ae4 specify lane resolve --command explain --ensure-worktree` before guessing from branch-only context.\n   - When lane resolution returns a materialized lane worktree, explain artifacts from that isolated worktree context so the explanation stays attached to the active feature lane.\n\n2. Resolve the stage artifact deterministically:\n   - If the user explicitly names a stage, honor it.\n   - If the user explicitly asks about project cognition, touched-area state, or brownfield runtime truth, resolve `.specify\u002Fproject-cognition\u002Fstatus.json` and the smallest matching query-backed artifact first.\n   - Explain handbook artifacts only when the user explicitly requests the compatibility\u002Fexport surfaces themselves.\n   - If the user explicitly asks for a compatibility\u002Fexport handbook, `PROJECT-HANDBOOK.md`, `architecture`, `structure`, `conventions`, `integrations`, `workflows`, `testing`, or `operations` artifact, resolve that artifact directly.\n   - Explain the architecture, cognition, or compatibility\u002Fexport atlas artifact directly instead of forcing a planning-stage fallback.\n   - Otherwise prefer the most advanced available artifact in this order:\n     - `tasks` -> `FEATURE_DIR\u002Ftasks.md`\n     - `plan` -> `FEATURE_DIR\u002Fplan.md`\n     - `specify` -> `FEATURE_DIR\u002Fspec.md`\n   - Supporting files:\n     - `specify`: also read `FEATURE_DIR\u002Falignment.md` and `FEATURE_DIR\u002Freferences.md` if present\n     - `clarify`: read `FEATURE_DIR\u002Fspec.md`, `FEATURE_DIR\u002Falignment.md`, and `FEATURE_DIR\u002Freferences.md` together, then explain the enhancement state as an extension of the current spec package\n     - `plan`: also read `FEATURE_DIR\u002Fresearch.md`, `FEATURE_DIR\u002Fdata-model.md`, `FEATURE_DIR\u002Fcontracts\u002F`, and `FEATURE_DIR\u002Fquickstart.md` when present\n     - `tasks`: also read `FEATURE_DIR\u002Fplan.md` and `FEATURE_DIR\u002Fspec.md` when needed for explanation\n     - `implement`: if there is no canonical implementation status artifact, explain that implementation status is unavailable from the current file set and fall back to the most recent planning artifact instead of guessing\n     - `project cognition`: read `.specify\u002Fproject-cognition\u002Fstatus.json` plus the smallest matching slice needed to explain ownership, dependencies, lifecycle, change impact, or verification routes accurately\n     - `compatibility\u002Fexport atlas`: read the explicitly requested handbook plus the smallest supporting export files needed to explain ownership, dependencies, lifecycle, change impact, or verification routes accurately\n\n3. Read the resolved artifact and any immediately supporting artifact needed to explain it accurately.\n   - If present, also read `.specify\u002Fmemory\u002Fconstitution.md` so the explanation honors the project constitution and its constraints on the current stage artifact.\n\n4. Before translating the artifact, assess workload shape and the current agent capability snapshot, then apply the shared policy contract: `choose_subagent_dispatch(command_name=\"explain\", snapshot, workload_shape)`.\n   - Persist the decision fields exactly: `execution_model: subagent-mandatory`, `dispatch_shape: one-subagent | parallel-subagents`, `execution_surface: native-subagents`.\n   - If repository inspection, artifact reading beyond already-provided context, or evidence cross-checking is needed, dispatch a bounded subagent lane before final explanation.\n   - If the artifact is fully provided in the current prompt and no repository inspection is needed, the leader may render the explanation directly because no substantive repository task is being executed.\n   - If required subagent dispatch is unavailable, record `subagent-blocked` and stop with the missing capability or packet requirement instead of treating coordinator-authored substantive work as the ordinary path.\n   - If collaboration is justified, keep `explain` lanes limited to:\n     - primary artifact reading\n     - supporting artifact cross-check\n   - Required join point:\n     - before rendering the final explanation\n   - Report the chosen strategy, reason, any `subagent-blocked` condition, and whether supporting cross-check lanes were used.\n\n5. Translate the artifact into plain language:\n   - what this stage is trying to accomplish\n   - what has already been decided\n   - what remains open or risky\n   - what the next stage will do with this information\n   - for project cognition and compatibility\u002Fexport atlas views: explain verified facts, inferred relationships, important unknowns, and the next relevant cognition slice or export view\n\n6. Present the explanation as a structured terminal UI built from open blocks, not a raw dump.\n\n## TUI Requirements\n\nThe output should use a polished terminal presentation with:\n\n- a stage header\n- a status block\n- an explanation block\n- a risk block\n- a next-step block\n\nThe explanation must remain stage-aware:\n\n- `specify`: explain the requirement package and what it means in everyday terms\n- `plan`: explain the implementation approach in plain language\n- `tasks`: explain what concrete work is about to happen\n- `implement`: explain progress, current scope, and active risks\n- `project cognition`: explain ownership, dependencies, lifecycle, change impact, confidence, and the next relevant cognition slice in plain language\n- `compatibility\u002Fexport atlas`: explain ownership, dependencies, lifecycle, change impact, confidence, and the next relevant export view in plain language\n\n## Rules\n\n- Keep the explanation grounded in the actual artifact on disk.\n- Use subagent lanes for explanation work that needs repository inspection or artifact cross-checking; leader synthesis is limited to fully supplied prompt context with no substantive repository task.\n- If a supporting cross-check lane is used, converge back to one final render step before presenting the explanation.\n- Use the user's current language for user-visible output unless literal command names, file paths, or fixed status values must remain unchanged.\n- Prefer clarity over jargon.\n- Do not invent missing state; if something is absent, say it is absent.\n\n## Codex Subagent Capability Discovery\n\n- Execution model: preserve the workflow's existing `subagent-mandatory`, `subagents-first`, `adaptive`, or `subagent-assisted` policy.\n- Dispatch shape: preserve the workflow's existing dispatch shape; use `subagent-blocked` only after the discovery step below fails or is unsafe.\n- Execution surface: prefer `native-subagents` when the current runtime supports it; use `none` only after recording the unavailable or unsafe surface.\n- Native subagent capability discovery: Before recording `subagent-blocked`, confirm the current runtime exposes `spawn_agent`, `wait_agent`, and `close_agent`; if they are not visible, use the active tool discovery mechanism for multi-agent or subagent tools first.\n- Do not record `subagent-blocked` until this capability discovery step is complete and the exact unavailable or unsafe surface is recorded.\n- Native subagent dispatch: Dispatch bounded subagents through `spawn_agent`.\n- Join behavior: Rejoin with `wait_agent`, integrate, then `close_agent`.\n- Preserve this workflow's existing packet, handoff, artifact, and result schema; this section only governs capability discovery before dispatch or blocked-state recording.\n","## Invocation Syntax\n\n- In this integration, invoke workflow skills with `$sp-plan`-style syntax.\n- References such as `\u002Fsp.plan`, `\u002Fsp.tasks`, or `next_command: \u002Fsp.plan` are canonical workflow-state identifiers and handoff values.\n- Preserve those canonical state tokens exactly in artifacts and workflow state; do not rewrite them to this integration's invocation syntax.\n\n\n\n## Workflow Contract Summary\n\n- **When to use**: The user needs to understand the current planning-stage artifact, project cognition state, or compatibility\u002Fexport atlas view before deciding whether to continue, revise, or proceed.\n- **Primary objective**: Translate the current artifact into plain language while staying faithful to what is actually on disk.\n- **Primary outputs**: A structured explanation only; do not rewrite stage artifacts or atlas documents unless another command explicitly requests it.\n- **Default handoff**: $sp-plan or \u002Fsp-tasks only after the user is satisfied with the current understanding and wants to advance.\n- **Execution note**: This summary is routing metadata only. Follow the full contract below end-to-end rather than inferring behavior from the description alone.\n\n## Blocked Exit Contract\n\nIf blocked after safe recovery, read and follow\n`.specify\u002Ftemplates\u002Fworkflow-blocker-template.md` and its JSON schema. Never\nreturn only an error or “ask a human”; preserve state and keep agent-capable\nrepair agent-owned. Set `human_action_required: true` only for authority,\ncredentials, protected systems, human decisions\u002Freviews, or physical access.\nTailor steps, expected results, failure paths, evidence, and resume action to\nCI, visual review, or product decisions. Never claim completion.\n\nFor a feature runtime blocker, do not invent `resume_argv` or overwrite an\nexisting blocker. The CLI returns a read-only `show_argv` and structured\n`resolution_action`; `next_argv` stays empty while evidence is missing. After\nthe criteria are proven, attach sanitized evidence using the action's declared\ninput and execute its base argv. It restores the same owner and keeps the full\nblocker audit.\n\n## User Input\n\n```text\n$ARGUMENTS\n```\n\nYou **MUST** consider the user input before proceeding (if not empty).\n\n## Objective\n\nExplain the current stage artifact in plain language so the user can understand what the system believes, what is settled, what remains open, and what the next stage would do.\n\n## Context\n\n- Primary inputs: the most relevant current stage artifact plus any immediately supporting artifacts needed to explain it accurately.\n- This command is explanation-only. It does not invent state that is absent and does not rewrite the underlying files.\n- If limited collaboration is used for a supporting cross-check, the final explanation still converges back to one render step.\n\n## Process\n\n- Resolve the current stage artifact deterministically.\n- Load only the supporting context needed to explain it faithfully.\n- Optionally run a bounded cross-check lane when the current artifact genuinely benefits from it.\n- Render one final structured explanation in the user's language.\n\n## Output Contract\n\n- Produce a stage-aware explanation with status, risk, and next-step framing.\n- Keep the explanation grounded in what is actually on disk.\n- Be explicit when implementation status or another expected artifact is absent.\n\n## Guardrails\n\n- Do not invent missing state.\n- Do not rewrite stage artifacts from inside `\u002Fsp-explain`.\n- Default to `leader-inline-fallback` only when no safe supporting subagent cross-check lane can be packetized and dispatched safely.\n\n## Project Learning\n\nThe CLI is the only agent-facing Learning read surface:\n\n1. Run `uvx --from git+https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Fspec-kit-plus.git@6fbbf08a0b6833bb783ec6b418d567776b197ae4 specify learning start --command '\u003Cclassic-command-name>' --format json` before deeper non-trivial work.\n2. Select summaries by applicability and triggers; use `uvx --from git+https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Fspec-kit-plus.git@6fbbf08a0b6833bb783ec6b418d567776b197ae4 specify learning list --command '\u003Cclassic-command-name>' --format json` only to filter or page.\n3. Execute one matching card's `show_argv`. Do not parse Learning storage.\n\nAfter minimal live inspection identifies a reused operation or changed entry point, rerun targeted recall with current code, tests, and task\u002Fcontract evidence, for example `uvx --from git+https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Fspec-kit-plus.git@6fbbf08a0b6833bb783ec6b418d567776b197ae4 specify learning list --command '\u003Cclassic-command-name>' --context 'operation_owner=\u003Cowner>' --context 'consumer_owner=\u003Cconsumer>' --context 'outcome=\u003Cresult-family>' --format json`. Do not derive these facets from archived specifications. An exact operation-owner match may surface a cross-command candidate even when the new consumer differs; treat it as a candidate, expand one `show_argv`, verify it against live evidence, and do not auto-apply it.\n\nWhen the entrypoint outcome audit is triggered, persist the live facets as `learning_context`, the contextual invocation as `learning_search_refs`, and returned refs as `learning_candidate_refs`. Record exactly one `applied`, `not_applicable`, or `deferred` item in `learning_dispositions` for every candidate. Do not silently ignore a candidate: applied Learning traces to requirement\u002Fconsequence refs, not-applicable needs current evidence, and deferred needs an explicit deferral ref.\n\n`start`, `list`, and `show` are read-only. Current repository evidence,\n`.specify\u002Fmemory\u002Fconstitution.md`, and explicit user direction override stale or\ncandidate Learning.\n\nAt closeout, corrections, retries, route changes, recovery, false leads, hidden\ndependencies, validation\u002Ftooling\u002Fstate\u002Fcognition gaps, constraints, and near\nmisses are capture signals. Prefer `uvx --from git+https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Fspec-kit-plus.git@6fbbf08a0b6833bb783ec6b418d567776b197ae4 specify learning capture-auto`\nfrom owning state; manual capture includes summary, problem, action, triggers,\nsuccess criteria, avoid items, exceptions, and evidence.\n\n- `fast`: skip unless the task escalates.\n- `accept`, `analyze`, `ask`, `auto`, `constitution`, `explain`,\n  `implement-teams`, `taskstoissues`, and `team`: consume-only; do not violate\n  their write boundaries to capture.\n- Other non-trivial workflows: consume before deeper work; capture reusable\n  signals at closeout or record a no-learning decision.\n\nThe `policy` returned by the CLI is authoritative when prompt wording drifts.\n\n## Mandatory Subagent Execution\n\nAll substantive tasks in ordinary `sp-*` workflows default to and must use subagents.\n\nThe leader orchestrates: route, split tasks, prepare task contracts, dispatch subagents, wait for structured handoffs, integrate results, verify, and update state.\n\nBefore dispatch, every subagent lane needs a task contract with objective, authoritative inputs, allowed read\u002Fwrite scope, forbidden paths, acceptance checks, verification evidence, and structured handoff format.\n\nUse `execution_model: subagent-mandatory`.\nUse `dispatch_shape: one-subagent | parallel-subagents`.\nUse `execution_surface: native-subagents`.\n\n\n## Outline\n\nGoal: Read the current stage artifact, project cognition artifact, or explicitly requested compatibility\u002Fexport atlas artifact and explain it in plain language so the user can understand what the system currently believes, what is decided, what is still open, and what the next phase or next relevant view will do.\n\n1. Run `.specify\u002Fscripts\u002Fpowershell\u002Fcheck-prerequisites.ps1 -Json -PathsOnly` from repo root once (`--json --paths-only` \u002F `-Json -PathsOnly`) and parse the available feature paths.\n   - If `FEATURE_DIR` is not already explicit, prefer `uvx --from git+https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Fspec-kit-plus.git@6fbbf08a0b6833bb783ec6b418d567776b197ae4 specify lane resolve --command explain --ensure-worktree` before guessing from branch-only context.\n   - When lane resolution returns a materialized lane worktree, explain artifacts from that isolated worktree context so the explanation stays attached to the active feature lane.\n\n2. Resolve the stage artifact deterministically:\n   - If the user explicitly names a stage, honor it.\n   - If the user explicitly asks about project cognition, touched-area state, or brownfield runtime truth, resolve `.specify\u002Fproject-cognition\u002Fstatus.json` and the smallest matching query-backed artifact first.\n   - Explain handbook artifacts only when the user explicitly requests the compatibility\u002Fexport surfaces themselves.\n   - If the user explicitly asks for a compatibility\u002Fexport handbook, `PROJECT-HANDBOOK.md`, `architecture`, `structure`, `conventions`, `integrations`, `workflows`, `testing`, or `operations` artifact, resolve that artifact directly.\n   - Explain the architecture, cognition, or compatibility\u002Fexport atlas artifact directly instead of forcing a planning-stage fallback.\n   - Otherwise prefer the most advanced available artifact in this order:\n     - `tasks` -> `FEATURE_DIR\u002Ftasks.md`\n     - `plan` -> `FEATURE_DIR\u002Fplan.md`\n     - `specify` -> `FEATURE_DIR\u002Fspec.md`\n   - Supporting files:\n     - `specify`: also read `FEATURE_DIR\u002Falignment.md` and `FEATURE_DIR\u002Freferences.md` if present\n     - `clarify`: read `FEATURE_DIR\u002Fspec.md`, `FEATURE_DIR\u002Falignment.md`, and `FEATURE_DIR\u002Freferences.md` together, then explain the enhancement state as an extension of the current spec package\n     - `plan`: also read `FEATURE_DIR\u002Fresearch.md`, `FEATURE_DIR\u002Fdata-model.md`, `FEATURE_DIR\u002Fcontracts\u002F`, and `FEATURE_DIR\u002Fquickstart.md` when present\n     - `tasks`: also read `FEATURE_DIR\u002Fplan.md` and `FEATURE_DIR\u002Fspec.md` when needed for explanation\n     - `implement`: if there is no canonical implementation status artifact, explain that implementation status is unavailable from the current file set and fall back to the most recent planning artifact instead of guessing\n     - `project cognition`: read `.specify\u002Fproject-cognition\u002Fstatus.json` plus the smallest matching slice needed to explain ownership, dependencies, lifecycle, change impact, or verification routes accurately\n     - `compatibility\u002Fexport atlas`: read the explicitly requested handbook plus the smallest supporting export files needed to explain ownership, dependencies, lifecycle, change impact, or verification routes accurately\n\n3. Read the resolved artifact and any immediately supporting artifact needed to explain it accurately.\n   - If present, also read `.specify\u002Fmemory\u002Fconstitution.md` so the explanation honors the project constitution and its constraints on the current stage artifact.\n\n4. Before translating the artifact, assess workload shape and the current agent capability snapshot, then apply the shared policy contract: `choose_subagent_dispatch(command_name=\"explain\", snapshot, workload_shape)`.\n   - Persist the decision fields exactly: `execution_model: subagent-mandatory`, `dispatch_shape: one-subagent | parallel-subagents`, `execution_surface: native-subagents`.\n   - If repository inspection, artifact reading beyond already-provided context, or evidence cross-checking is needed, dispatch a bounded subagent lane before final explanation.\n   - If the artifact is fully provided in the current prompt and no repository inspection is needed, the leader may render the explanation directly because no substantive repository task is being executed.\n   - If required subagent dispatch is unavailable, record `subagent-blocked` and stop with the missing capability or packet requirement instead of treating coordinator-authored substantive work as the ordinary path.\n   - If collaboration is justified, keep `explain` lanes limited to:\n     - primary artifact reading\n     - supporting artifact cross-check\n   - Required join point:\n     - before rendering the final explanation\n   - Report the chosen strategy, reason, any `subagent-blocked` condition, and whether supporting cross-check lanes were used.\n\n5. Translate the artifact into plain language:\n   - what this stage is trying to accomplish\n   - what has already been decided\n   - what remains open or risky\n   - what the next stage will do with this information\n   - for project cognition and compatibility\u002Fexport atlas views: explain verified facts, inferred relationships, important unknowns, and the next relevant cognition slice or export view\n\n6. Present the explanation as a structured terminal UI built from open blocks, not a raw dump.\n\n## TUI Requirements\n\nThe output should use a polished terminal presentation with:\n\n- a stage header\n- a status block\n- an explanation block\n- a risk block\n- a next-step block\n\nThe explanation must remain stage-aware:\n\n- `specify`: explain the requirement package and what it means in everyday terms\n- `plan`: explain the implementation approach in plain language\n- `tasks`: explain what concrete work is about to happen\n- `implement`: explain progress, current scope, and active risks\n- `project cognition`: explain ownership, dependencies, lifecycle, change impact, confidence, and the next relevant cognition slice in plain language\n- `compatibility\u002Fexport atlas`: explain ownership, dependencies, lifecycle, change impact, confidence, and the next relevant export view in plain language\n\n## Rules\n\n- Keep the explanation grounded in the actual artifact on disk.\n- Use subagent lanes for explanation work that needs repository inspection or artifact cross-checking; leader synthesis is limited to fully supplied prompt context with no substantive repository task.\n- If a supporting cross-check lane is used, converge back to one final render step before presenting the explanation.\n- Use the user's current language for user-visible output unless literal command names, file paths, or fixed status values must remain unchanged.\n- Prefer clarity over jargon.\n- Do not invent missing state; if something is absent, say it is absent.\n\n## Codex Subagent Capability Discovery\n\n- Execution model: preserve the workflow's existing `subagent-mandatory`, `subagents-first`, `adaptive`, or `subagent-assisted` policy.\n- Dispatch shape: preserve the workflow's existing dispatch shape; use `subagent-blocked` only after the discovery step below fails or is unsafe.\n- Execution surface: prefer `native-subagents` when the current runtime supports it; use `none` only after recording the unavailable or unsafe surface.\n- Native subagent capability discovery: Before recording `subagent-blocked`, confirm the current runtime exposes `spawn_agent`, `wait_agent`, and `close_agent`; if they are not visible, use the active tool discovery mechanism for multi-agent or subagent tools first.\n- Do not record `subagent-blocked` until this capability discovery step is complete and the exact unavailable or unsafe surface is recorded.\n- Native subagent dispatch: Dispatch bounded subagents through `spawn_agent`.\n- Join behavior: Rejoin with `wait_agent`, integrate, then `close_agent`.\n- Preserve this workflow's existing packet, handoff, artifact, and result schema; this section only governs capability discovery before dispatch or blocked-state recording.\n",{"name":5,"metadata":24,"description":7,"compatibility":27},{"author":25,"source":26},"github-spec-kit","templates\u002Fcommands\u002Fexplain.md","Requires spec-kit project structure with .specify\u002F directory","main","021f5cbe02157229460a577e9a585f2da6d78cb0",".codex\u002Fskills\u002Fsp-explain","https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck","https:\u002F\u002Fgithub.com\u002Fchenziyang110","2026-08-07 18:10:54",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add chenziyang110\u002Flaunchdeck --skill sp-explain",{"tool":40,"command":41},"bunx","bunx skills add chenziyang110\u002Flaunchdeck --skill sp-explain",{"tool":43,"command":44},"pnpm","pnpm dlx skills add chenziyang110\u002Flaunchdeck --skill sp-explain","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fsp-explain\u002FSKILL.md",true,[],[49,56,62,68,75,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7875F3HQ1GF5F6BR36KY3JE","launchdeck-agent","Codex host adapter contract fixture for Launchdeck.","https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fagent-hosts\u002Fcodex\u002Fskill\u002FSKILL.md",[],[],{"skillNo":57,"name":51,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7875DV2DQR33K1NFJHKAMZP","Claude host adapter contract fixture for Launchdeck.","https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fagent-hosts\u002Fclaude\u002Fskill\u002FSKILL.md",[],[],{"skillNo":63,"name":51,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M78759JQ7A6FQ8KDQTNYS3X9","Use this skill aggressively for local project lifecycle operations even when the user does not mention Launchdeck: start this project, run the dev server, dev, build, test, restart service, stop service, show logs, inspect ports, port is occupied, clean cache; and when the user explicitly asks to configure this local project for Launchdeck or create or generate a project-adapted `.launchdeck.yml`, including 为这个项目生成 Launchdeck 配置. Do not use for ordinary code edits, docs-only work, general explanations, API design discussion, or production deployment unless the user also asks to operate or configure a local project or service.","https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002Fagent\u002Finstaller-payload\u002Fskill\u002Flaunchdeck-agent\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M78753ZJQ7G2CZT1W1G8WRJV","zig-testing","Use ONLY when user explicitly requests Zig test code, built-in test runner configuration,\ntest failure diagnosis, or coverage for Zig projects.\n\nTriggers: \"write test zig\", \"zig test\", \"testing.allocator\", \"zig coverage\",\n\"comptime test\", \"zig expectError\", \"zig snapshot test\", \"zig fuzz\".\n\nDo NOT activate for: general Zig coding without test context, build.zig configuration\nfor non-test targets, Zig compiler errors, or Zig build system setup.","https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.specify\u002Ftemplates\u002Fpassive-skills\u002Fzig-testing\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":80,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M78750JXY4Z5D5W1EX3PQ31Z","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.specify\u002Ftemplates\u002Fpassive-skills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.specify\u002Ftemplates\u002Fpassive-skills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7874X2T83EQQFRCEY5SJJVC","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.specify\u002Ftemplates\u002Fpassive-skills\u002Fverification-before-completion\u002FSKILL.md",[],[]]