[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M786TTM5FEKP0APGDGHXES9H":3,"skill-same:01M786TTM5FEKP0APGDGHXES9H":58},{"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},"01M786TTM5FEKP0APGDGHXES9H","sp-prd-scan",null,"Use when an existing repository needs reconstruction-grade scan outputs before a PRD suite can be compiled.","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-prd-scan\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"sp-prd-scan\"\ndescription: \"Use when an existing repository needs reconstruction-grade scan outputs before a PRD suite can be compiled.\"\ncompatibility: \"Requires spec-kit project structure with .specify\u002F directory\"\nmetadata:\n  author: \"github-spec-kit\"\n  source: \"templates\u002Fcommands\u002Fprd-scan.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## 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# `\u002Fsp.prd-scan` Reconstruction Scan\n\n## Workflow Contract Summary\n\nThis summary is routing metadata only. The full workflow contract is the frontmatter plus the sections below.\n\n- Use `sp-prd-scan` for read-only reconstruction investigation.\n- Primary truth source: current repository reality plus the `C:\\Users\\11034\\.specify\\bin\\project-cognition.exe query` bundle and compatibility\u002Fexport evidence when explicitly needed.\n- Primary terminal state: completed scan package under `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002F`.\n- Stable freshness state: `.specify\u002Fprd\u002Fstatus.json`.\n- Default handoff: `\u002Fsp-prd-build`.\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[AGENT] For project-cognition-backed semantic intake, routing, audit, resume, or final-claim gates, read `references\u002Fsemantic-work-contract.md`.\n\n## Detailed References\n\nRead [Reference index](references\u002FINDEX.md) before applying shared semantic contracts.\n\n- [semantic work contract](references\u002Fsemantic-work-contract.md)\n\n## Objective\n\n[AGENT] Produce a reconstruction-grade scan package that lets `sp-prd-build` compile a PRD suite without rereading the repository.\n\nThe scan phase is a read-only reconstruction investigation. It must harvest enough grounded detail about each `capability`, `artifact`, and `boundary` to prove whether the package is reconstruction-ready or should be marked `blocked-by-gap`.\nEvery consequential claim must preserve `Evidence`, `Inference`, and `Unknown` labeling semantics instead of collapsing them into one unmarked narrative.\n\n## Context\n\nRequired context inputs:\n\n- **Project cognition gate:** query the active project's runtime before broad\n  repository reads.\n\n  Run or emulate:\n\n  ```text\n  C:\\Users\\11034\\.specify\\bin\\project-cognition.exe compass --intent research '--query=\"$ARGUMENTS\"' --format json\n  ```\n\n  After the default compass packet, run the advanced `lexicon -> semantic_intake -> query` path only when `compass_state`, coverage diagnostics, localization, or live evidence requires explicit concept decisions. In that escalation, use `C:\\Users\\11034\\.specify\\bin\\project-cognition.exe lexicon --mode catalog` as the alias catalog, write agent-authored `semantic_intake` and `concept_decisions`, then run `C:\\Users\\11034\\.specify\\bin\\project-cognition.exe query --query-plan \"\u003Cquery_plan_json>\"`; include `query_plan`, `semantic_intake`, `concept_decisions`, `covered_facets`, `missing_facets`, `match_sources`, `lexicon_generation_id`, `repository_search_terms`, project-language search terms, and facet coverage; do not search only the raw user words before source search. Agent-owned semantic normalization remains mandatory: `agent_normalization` and raw lexicon ranking are bootstrap signals only; if `agent_normalization` is omitted, treat it as `required=false`; use `write_semantic_intake_from_alias_catalog` when needed. Raw lexicon ranking is only a bootstrap; CJK or mixed CJK\u002FASCII input still requires agent-owned normalization even when positive raw lexical matches exist. The agent still owns translation. Readiness values are `query_ready`, `review`, `needs_rebuild`, `blocked`, and `unsupported_runtime`.\n\n  Use the returned readiness:\n\n  - `query_ready`: read top-level `minimal_live_reads` first, then use lane-level `first_pass_paths` reasons.\n  - `review`: perform only the returned `minimal_live_reads` before continuing and inspect `coverage_diagnostics`.\n  - `needs_rebuild`: route by `recommended_next_action.action_id`, not readiness alone. Preserve resumable actions such as `complete_scan_packets`; only `action_id=project_cognition.rebuild` may consume `rebuild_reasons[]` and `recommended_next_action.workflow_routes.classic.steps` as a rebuild handoff.\n  - `blocked`: report the blocking runtime issue and continue with live evidence only where this workflow allows degraded navigation.\n- `PROJECT-HANDBOOK.md` only when compatibility\u002Fexport evidence is explicitly relevant.\n- `.specify\u002Fprd\u002Fstatus.json` as the stable PRD scan freshness record when present.\n- Current repository evidence from code, docs, tests, routes, UI surfaces, service surfaces, data models, integrations, configuration, and deployment surfaces.\n- Existing `workflow-state.md` under `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002F` when resuming an interrupted run.\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 scope, forbidden actions, 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`.\nEach delegated lane produces a `PrdScanPacket`: a read-only evidence packet with enough cited detail for the build step to synthesize the final archive without rereading the repository.\n\n## Unified Critical Item Families\n\n1. Main Capability Chains\n2. External Entrypoints and Command Surfaces\n3. State Machines and Flow Control\n4. Data and Persistence Contracts\n5. Configuration and Behavior Switches\n6. Protocol and Boundary Contracts\n7. Error Semantics and Recovery Behavior\n8. Verification and Regression Entrypoints\n\n## Evidence Depth Model\n\n- `L1 Exists`: the item is discovered and tied to at least one repository surface.\n- `L2 Surface`: the user-visible, command, API, config, data, or boundary shape is captured.\n- `L3 Behavioral`: normal behavior, edge behavior, state changes, and failure behavior are grounded in evidence.\n- `L4 Reconstruction-Ready`: enough structure, contracts, and verification evidence exist to recreate the behavior without critical unknowns.\n\n## Hard Boundary\n\n- `sp-prd-scan` must not write `master\u002Fmaster-pack.md`.\n- `sp-prd-scan` must not write `exports\u002F**`.\n- `sp-prd-scan` must not claim the PRD suite is complete.\n\n## PRD Run State Protocol\n\n- `workflow-state.md` under `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002F` is the resumable state surface for `sp-prd-scan` and `sp-prd-build`.\n- [AGENT] Create or resume `workflow-state.md` before substantial scan work.\n- If `workflow-state.md` exists with `active_command: sp-prd-scan` and a non-terminal scan state, resume from it instead of rebuilding intent from chat memory.\n- Track at least:\n  - `active_command: sp-prd-scan`\n  - `status: scanning | synthesizing | blocked | ready-for-build`\n  - `scan_status: pending | scanning | blocked | complete`\n  - `build_status`\n  - `freshness_mode`\n  - `classification`\n  - `selected_capabilities`\n  - `selected_boundaries`\n  - `selected_artifacts`\n  - `current_packet`\n  - `accepted_packet_results`\n  - `rejected_packet_results`\n  - `failed_readiness_checks`\n  - `next_action`\n  - `next_command`\n  - `handoff_reason`\n  - `open_gaps`\n\n## Process\n\n1. Route and initialize the PRD run under `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002F`.\n2. Load brownfield context and select the smallest relevant repository surfaces.\n3. Check `.specify\u002Fprd\u002Fstatus.json` freshness before scoping the scan.\n4. Route `fresh` status to status confirmation only unless the user explicitly requests a new run.\n5. Route `targeted-stale` status to a bounded scan of the changed source, test, and documentation surfaces plus any directly adjacent capability boundaries.\n6. Route `full-stale` status to a full reconstruction scan across command, workflow, integration, configuration, and shared-runtime surfaces.\n7. Triage `capability`, `artifact`, and `boundary` objects before broad synthesis.\n8. Assign each capability a tier: `critical`, `high`, `standard`, or `auxiliary`.\n9. Before broad scan fan-out begins, assess workload shape and the current agent capability snapshot, then apply the shared policy contract: `choose_subagent_dispatch(command_name=\"prd-scan\", snapshot, workload_shape)`.\n10. Persist the decision fields exactly: `execution_model: subagent-mandatory`, `dispatch_shape: one-subagent | parallel-subagents`, `execution_surface: native-subagents`.\n11. Decision order is fixed:\n    - One safe validated scan lane -> `one-subagent` on `native-subagents` when available.\n    - Two or more safe read-only scan lanes -> `parallel-subagents` on `native-subagents` when available.\n    - No safe lane, incomplete packet, or unavailable delegation -> `subagent-blocked` with a recorded reason.\n12. Compile a validated `PrdScanPacket` before dispatch or `subagent-blocked` status.\n13. For `one-subagent`, dispatch one read-only scan lane once a validated `PrdScanPacket` exists. If the packet is incomplete, compile the missing fields before dispatch; if dispatch is unavailable, record `subagent-blocked` with the blocker and stop for escalation or recovery before broad scan work continues.\n14. If collaboration is justified, keep `prd-scan` lanes read-only and limited to reconstruction evidence gathering, tier classification, and packet drafting.\n15. Required join points:\n    - before freezing ledgers and machine-readable contracts\n    - before declaring the package ready for `sp-prd-build`\n16. The leader owns final ledger normalization, contract updates, and packet quality even when subagents help with scan work.\n17. For `critical` and `high` capabilities, capture stronger reconstruction detail: structure, producers, consumers, constraints, compatibility behavior, and failure behavior.\n18. Build `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fartifact-contracts.json` and `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Freconstruction-checklist.json`.\n19. Generate scan packets and evidence notes that explain structure, producers, consumers, constraints, and failure behavior while preserving `Evidence`, `Inference`, and `Unknown`.\n20. Refuse handoff if any `critical` capability lacks reconstruction-ready support. `high` capabilities must not be waved through with path-only evidence; keep the status explicit as `blocked-by-gap` when evidence is insufficient.\n\n## Output Contract\n\nThe scan phase writes only the reconstruction package:\n\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fworkflow-state.md`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fprd-scan.md`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fcoverage-ledger.md`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fcoverage-ledger.json`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fcapability-ledger.json`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fartifact-contracts.json`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Freconstruction-checklist.json`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fentrypoint-ledger.json`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fconfig-contracts.json`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fprotocol-contracts.json`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fstate-machines.json`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Ferror-semantics.json`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fverification-surfaces.json`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fscan-packets\u002F\u003Clane-id>.md`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fevidence\u002F**`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fworker-results\u002F**`\n- `.specify\u002Fprd\u002Fstatus.json` when initializing a successful scan and the stable status file is absent\n\nThese artifacts are the authoritative scan bundle for `sp-prd-build`; they are not draft exports.\n\n## Compile And Validate PrdScanPacket Inputs\n\n- [AGENT] Compile a validated `PrdScanPacket` before dispatch or `subagent-blocked` status.\n- A valid `PrdScanPacket` must include:\n  - `lane_id`\n  - `mode: read_only`\n  - `scope`\n  - `capability_ids`\n  - `artifact_ids`\n  - `boundary_ids`\n  - `required_reads`\n  - `excluded_paths`\n  - `required_questions`\n  - `expected_outputs`\n  - `contract_targets`\n  - `forbidden_actions`\n  - `result_handoff_path`\n  - `join_points`\n  - `minimum_verification`\n  - `blocked_conditions`\n- Hard rule: do not dispatch from raw scan prose or broad chat instructions alone.\n\n## PrdScanPacket Dispatch\n\n- If no safe lane exists, the packet is incomplete, or delegation is unavailable, record `subagent-blocked` with the blocker and stop for escalation or recovery before broad scan work continues.\n- Raw inventory notes or raw chat summaries are not sufficient subagent inputs or outputs.\n- Each dispatched lane needs a validated `PrdScanPacket` and must return a structured handoff with inspected paths, key facts, confidence, blockers, and recommended contract updates.\n- Idle subagent output is not an accepted scan result.\n- The leader must wait for every dispatched lane and consume its structured handoff before finalizing ledgers, writing scan packets, or marking the scan complete.\n\n## Worker Result Contract\n\nEvery scan-lane result must include:\n\n- `lane_id`\n- `reported_status: done | done_with_concerns | blocked | needs_context`\n- `paths_read`\n- `key_facts`\n- `evidence_refs`\n- `recommended_contract_updates`\n- `confidence`\n- `unknowns`\n- `minimum_verification`\n- `result_handoff_path`\n\nReject results that omit `paths_read`, collapse evidence into prose-only summary, hide `unknowns`, or leave contract impact undefined where one is expected.\n\n## Quality Gates\n\n- Stable Status Gate: `.specify\u002Fprd\u002Fstatus.json` must be consulted or initialized, and the run must record whether freshness is `fresh`, `targeted-stale`, or `full-stale`.\n- Capability Triage Gate: each capability must be assigned `critical`, `high`, `standard`, or `auxiliary` before scan completion can be claimed.\n- Critical Depth Gate: each `critical` capability must be explicitly marked `reconstruction-ready` or `blocked-by-gap`, with structure, producer-consumer, constraint, and failure coverage captured.\n- High Capability Gate: each `high` capability must have more than path-only evidence and must record reconstruction-relevant structure and boundary behavior.\n- Artifact Contract Gate: important structures must land in `artifact-contracts.json`.\n- Checklist Gate: recreation blockers and remaining `Unknown` items must be visible in `reconstruction-checklist.json`.\n- Evidence Label Gate: scan outputs must preserve `Evidence`, `Inference`, and `Unknown` labeling semantics.\n\n## Guardrails\n\n- Do not write final PRD exports in `sp-prd-scan`.\n- Do not treat path discovery as sufficient reconstruction evidence.\n- Do not let `critical` or `high` capabilities pass with shallow evidence only.\n- Do not hide unknowns that block a later build step.\n- When refusal is required, report the smallest safe repair instead of softening the gap into narrative prose.\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## 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# `\u002Fsp.prd-scan` Reconstruction Scan\n\n## Workflow Contract Summary\n\nThis summary is routing metadata only. The full workflow contract is the frontmatter plus the sections below.\n\n- Use `sp-prd-scan` for read-only reconstruction investigation.\n- Primary truth source: current repository reality plus the `C:\\Users\\11034\\.specify\\bin\\project-cognition.exe query` bundle and compatibility\u002Fexport evidence when explicitly needed.\n- Primary terminal state: completed scan package under `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002F`.\n- Stable freshness state: `.specify\u002Fprd\u002Fstatus.json`.\n- Default handoff: `\u002Fsp-prd-build`.\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[AGENT] For project-cognition-backed semantic intake, routing, audit, resume, or final-claim gates, read `references\u002Fsemantic-work-contract.md`.\n\n## Detailed References\n\nRead [Reference index](references\u002FINDEX.md) before applying shared semantic contracts.\n\n- [semantic work contract](references\u002Fsemantic-work-contract.md)\n\n## Objective\n\n[AGENT] Produce a reconstruction-grade scan package that lets `sp-prd-build` compile a PRD suite without rereading the repository.\n\nThe scan phase is a read-only reconstruction investigation. It must harvest enough grounded detail about each `capability`, `artifact`, and `boundary` to prove whether the package is reconstruction-ready or should be marked `blocked-by-gap`.\nEvery consequential claim must preserve `Evidence`, `Inference`, and `Unknown` labeling semantics instead of collapsing them into one unmarked narrative.\n\n## Context\n\nRequired context inputs:\n\n- **Project cognition gate:** query the active project's runtime before broad\n  repository reads.\n\n  Run or emulate:\n\n  ```text\n  C:\\Users\\11034\\.specify\\bin\\project-cognition.exe compass --intent research '--query=\"$ARGUMENTS\"' --format json\n  ```\n\n  After the default compass packet, run the advanced `lexicon -> semantic_intake -> query` path only when `compass_state`, coverage diagnostics, localization, or live evidence requires explicit concept decisions. In that escalation, use `C:\\Users\\11034\\.specify\\bin\\project-cognition.exe lexicon --mode catalog` as the alias catalog, write agent-authored `semantic_intake` and `concept_decisions`, then run `C:\\Users\\11034\\.specify\\bin\\project-cognition.exe query --query-plan \"\u003Cquery_plan_json>\"`; include `query_plan`, `semantic_intake`, `concept_decisions`, `covered_facets`, `missing_facets`, `match_sources`, `lexicon_generation_id`, `repository_search_terms`, project-language search terms, and facet coverage; do not search only the raw user words before source search. Agent-owned semantic normalization remains mandatory: `agent_normalization` and raw lexicon ranking are bootstrap signals only; if `agent_normalization` is omitted, treat it as `required=false`; use `write_semantic_intake_from_alias_catalog` when needed. Raw lexicon ranking is only a bootstrap; CJK or mixed CJK\u002FASCII input still requires agent-owned normalization even when positive raw lexical matches exist. The agent still owns translation. Readiness values are `query_ready`, `review`, `needs_rebuild`, `blocked`, and `unsupported_runtime`.\n\n  Use the returned readiness:\n\n  - `query_ready`: read top-level `minimal_live_reads` first, then use lane-level `first_pass_paths` reasons.\n  - `review`: perform only the returned `minimal_live_reads` before continuing and inspect `coverage_diagnostics`.\n  - `needs_rebuild`: route by `recommended_next_action.action_id`, not readiness alone. Preserve resumable actions such as `complete_scan_packets`; only `action_id=project_cognition.rebuild` may consume `rebuild_reasons[]` and `recommended_next_action.workflow_routes.classic.steps` as a rebuild handoff.\n  - `blocked`: report the blocking runtime issue and continue with live evidence only where this workflow allows degraded navigation.\n- `PROJECT-HANDBOOK.md` only when compatibility\u002Fexport evidence is explicitly relevant.\n- `.specify\u002Fprd\u002Fstatus.json` as the stable PRD scan freshness record when present.\n- Current repository evidence from code, docs, tests, routes, UI surfaces, service surfaces, data models, integrations, configuration, and deployment surfaces.\n- Existing `workflow-state.md` under `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002F` when resuming an interrupted run.\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 scope, forbidden actions, 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`.\nEach delegated lane produces a `PrdScanPacket`: a read-only evidence packet with enough cited detail for the build step to synthesize the final archive without rereading the repository.\n\n## Unified Critical Item Families\n\n1. Main Capability Chains\n2. External Entrypoints and Command Surfaces\n3. State Machines and Flow Control\n4. Data and Persistence Contracts\n5. Configuration and Behavior Switches\n6. Protocol and Boundary Contracts\n7. Error Semantics and Recovery Behavior\n8. Verification and Regression Entrypoints\n\n## Evidence Depth Model\n\n- `L1 Exists`: the item is discovered and tied to at least one repository surface.\n- `L2 Surface`: the user-visible, command, API, config, data, or boundary shape is captured.\n- `L3 Behavioral`: normal behavior, edge behavior, state changes, and failure behavior are grounded in evidence.\n- `L4 Reconstruction-Ready`: enough structure, contracts, and verification evidence exist to recreate the behavior without critical unknowns.\n\n## Hard Boundary\n\n- `sp-prd-scan` must not write `master\u002Fmaster-pack.md`.\n- `sp-prd-scan` must not write `exports\u002F**`.\n- `sp-prd-scan` must not claim the PRD suite is complete.\n\n## PRD Run State Protocol\n\n- `workflow-state.md` under `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002F` is the resumable state surface for `sp-prd-scan` and `sp-prd-build`.\n- [AGENT] Create or resume `workflow-state.md` before substantial scan work.\n- If `workflow-state.md` exists with `active_command: sp-prd-scan` and a non-terminal scan state, resume from it instead of rebuilding intent from chat memory.\n- Track at least:\n  - `active_command: sp-prd-scan`\n  - `status: scanning | synthesizing | blocked | ready-for-build`\n  - `scan_status: pending | scanning | blocked | complete`\n  - `build_status`\n  - `freshness_mode`\n  - `classification`\n  - `selected_capabilities`\n  - `selected_boundaries`\n  - `selected_artifacts`\n  - `current_packet`\n  - `accepted_packet_results`\n  - `rejected_packet_results`\n  - `failed_readiness_checks`\n  - `next_action`\n  - `next_command`\n  - `handoff_reason`\n  - `open_gaps`\n\n## Process\n\n1. Route and initialize the PRD run under `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002F`.\n2. Load brownfield context and select the smallest relevant repository surfaces.\n3. Check `.specify\u002Fprd\u002Fstatus.json` freshness before scoping the scan.\n4. Route `fresh` status to status confirmation only unless the user explicitly requests a new run.\n5. Route `targeted-stale` status to a bounded scan of the changed source, test, and documentation surfaces plus any directly adjacent capability boundaries.\n6. Route `full-stale` status to a full reconstruction scan across command, workflow, integration, configuration, and shared-runtime surfaces.\n7. Triage `capability`, `artifact`, and `boundary` objects before broad synthesis.\n8. Assign each capability a tier: `critical`, `high`, `standard`, or `auxiliary`.\n9. Before broad scan fan-out begins, assess workload shape and the current agent capability snapshot, then apply the shared policy contract: `choose_subagent_dispatch(command_name=\"prd-scan\", snapshot, workload_shape)`.\n10. Persist the decision fields exactly: `execution_model: subagent-mandatory`, `dispatch_shape: one-subagent | parallel-subagents`, `execution_surface: native-subagents`.\n11. Decision order is fixed:\n    - One safe validated scan lane -> `one-subagent` on `native-subagents` when available.\n    - Two or more safe read-only scan lanes -> `parallel-subagents` on `native-subagents` when available.\n    - No safe lane, incomplete packet, or unavailable delegation -> `subagent-blocked` with a recorded reason.\n12. Compile a validated `PrdScanPacket` before dispatch or `subagent-blocked` status.\n13. For `one-subagent`, dispatch one read-only scan lane once a validated `PrdScanPacket` exists. If the packet is incomplete, compile the missing fields before dispatch; if dispatch is unavailable, record `subagent-blocked` with the blocker and stop for escalation or recovery before broad scan work continues.\n14. If collaboration is justified, keep `prd-scan` lanes read-only and limited to reconstruction evidence gathering, tier classification, and packet drafting.\n15. Required join points:\n    - before freezing ledgers and machine-readable contracts\n    - before declaring the package ready for `sp-prd-build`\n16. The leader owns final ledger normalization, contract updates, and packet quality even when subagents help with scan work.\n17. For `critical` and `high` capabilities, capture stronger reconstruction detail: structure, producers, consumers, constraints, compatibility behavior, and failure behavior.\n18. Build `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fartifact-contracts.json` and `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Freconstruction-checklist.json`.\n19. Generate scan packets and evidence notes that explain structure, producers, consumers, constraints, and failure behavior while preserving `Evidence`, `Inference`, and `Unknown`.\n20. Refuse handoff if any `critical` capability lacks reconstruction-ready support. `high` capabilities must not be waved through with path-only evidence; keep the status explicit as `blocked-by-gap` when evidence is insufficient.\n\n## Output Contract\n\nThe scan phase writes only the reconstruction package:\n\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fworkflow-state.md`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fprd-scan.md`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fcoverage-ledger.md`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fcoverage-ledger.json`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fcapability-ledger.json`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fartifact-contracts.json`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Freconstruction-checklist.json`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fentrypoint-ledger.json`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fconfig-contracts.json`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fprotocol-contracts.json`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fstate-machines.json`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Ferror-semantics.json`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fverification-surfaces.json`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fscan-packets\u002F\u003Clane-id>.md`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fevidence\u002F**`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fworker-results\u002F**`\n- `.specify\u002Fprd\u002Fstatus.json` when initializing a successful scan and the stable status file is absent\n\nThese artifacts are the authoritative scan bundle for `sp-prd-build`; they are not draft exports.\n\n## Compile And Validate PrdScanPacket Inputs\n\n- [AGENT] Compile a validated `PrdScanPacket` before dispatch or `subagent-blocked` status.\n- A valid `PrdScanPacket` must include:\n  - `lane_id`\n  - `mode: read_only`\n  - `scope`\n  - `capability_ids`\n  - `artifact_ids`\n  - `boundary_ids`\n  - `required_reads`\n  - `excluded_paths`\n  - `required_questions`\n  - `expected_outputs`\n  - `contract_targets`\n  - `forbidden_actions`\n  - `result_handoff_path`\n  - `join_points`\n  - `minimum_verification`\n  - `blocked_conditions`\n- Hard rule: do not dispatch from raw scan prose or broad chat instructions alone.\n\n## PrdScanPacket Dispatch\n\n- If no safe lane exists, the packet is incomplete, or delegation is unavailable, record `subagent-blocked` with the blocker and stop for escalation or recovery before broad scan work continues.\n- Raw inventory notes or raw chat summaries are not sufficient subagent inputs or outputs.\n- Each dispatched lane needs a validated `PrdScanPacket` and must return a structured handoff with inspected paths, key facts, confidence, blockers, and recommended contract updates.\n- Idle subagent output is not an accepted scan result.\n- The leader must wait for every dispatched lane and consume its structured handoff before finalizing ledgers, writing scan packets, or marking the scan complete.\n\n## Worker Result Contract\n\nEvery scan-lane result must include:\n\n- `lane_id`\n- `reported_status: done | done_with_concerns | blocked | needs_context`\n- `paths_read`\n- `key_facts`\n- `evidence_refs`\n- `recommended_contract_updates`\n- `confidence`\n- `unknowns`\n- `minimum_verification`\n- `result_handoff_path`\n\nReject results that omit `paths_read`, collapse evidence into prose-only summary, hide `unknowns`, or leave contract impact undefined where one is expected.\n\n## Quality Gates\n\n- Stable Status Gate: `.specify\u002Fprd\u002Fstatus.json` must be consulted or initialized, and the run must record whether freshness is `fresh`, `targeted-stale`, or `full-stale`.\n- Capability Triage Gate: each capability must be assigned `critical`, `high`, `standard`, or `auxiliary` before scan completion can be claimed.\n- Critical Depth Gate: each `critical` capability must be explicitly marked `reconstruction-ready` or `blocked-by-gap`, with structure, producer-consumer, constraint, and failure coverage captured.\n- High Capability Gate: each `high` capability must have more than path-only evidence and must record reconstruction-relevant structure and boundary behavior.\n- Artifact Contract Gate: important structures must land in `artifact-contracts.json`.\n- Checklist Gate: recreation blockers and remaining `Unknown` items must be visible in `reconstruction-checklist.json`.\n- Evidence Label Gate: scan outputs must preserve `Evidence`, `Inference`, and `Unknown` labeling semantics.\n\n## Guardrails\n\n- Do not write final PRD exports in `sp-prd-scan`.\n- Do not treat path discovery as sufficient reconstruction evidence.\n- Do not let `critical` or `high` capabilities pass with shallow evidence only.\n- Do not hide unknowns that block a later build step.\n- When refusal is required, report the smallest safe repair instead of softening the gap into narrative prose.\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\u002Fprd-scan.md","Requires spec-kit project structure with .specify\u002F directory","main","021f5cbe02157229460a577e9a585f2da6d78cb0",".codex\u002Fskills\u002Fsp-prd-scan","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-prd-scan",{"tool":40,"command":41},"bunx","bunx skills add chenziyang110\u002Flaunchdeck --skill sp-prd-scan",{"tool":43,"command":44},"pnpm","pnpm dlx skills add chenziyang110\u002Flaunchdeck --skill sp-prd-scan","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fsp-prd-scan\u002FSKILL.md",true,[48,54],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002FINDEX.md","REFERENCE","参考文档",605,"https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fsp-prd-scan\u002Freferences\u002FINDEX.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fsemantic-work-contract.md",32438,"https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fsp-prd-scan\u002Freferences\u002Fsemantic-work-contract.md",[59,66,72,78,85,94],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"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":67,"name":61,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"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":73,"name":61,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"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":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":89,"licenseFileUrl":90,"sourceHtmlUrl":91,"categories":92,"keywords":93,"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":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"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",[],[]]