[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72SA5NW4HD4XFVNYB9DPBAR":3,"skill-same:01M72SA5NW4HD4XFVNYB9DPBAR":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M72SA5NW4HD4XFVNYB9DPBAR","speckit-analyze",null,"Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.","EHotwagner\u002FFS-Skia-UI","EHotwagner","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1645484?v=4","01M72S7CTBDPQDQHQJKKHY87K9","01M72S7CVFD0JN82RVX21NFEVC",2,"MIT","https:\u002F\u002Fgithub.com\u002FEHotwagner\u002FFS-Skia-UI\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fspeckit-analyze\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: \"speckit-analyze\"\ndescription: \"Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.\"\ncompatibility: \"Requires spec-kit project structure with .specify\u002F directory\"\nmetadata:\n  author: \"github-spec-kit\"\n  source: \"templates\u002Fcommands\u002Fanalyze.md\"\n---\n\n\n## User Input\n\n```text\n$ARGUMENTS\n```\n\nYou **MUST** consider the user input before proceeding (if not empty).\n\n## Pre-Execution Checks\n\n**Check for extension hooks (before analysis)**:\n- Discover hooks across **all** extension files (multi-file discovery), not just the central file:\n  - Read `.specify\u002Fextensions.yml` from the project root (if present) and collect entries under the `hooks.before_analyze` key.\n  - Then enumerate every `.specify\u002Fextensions\u002F*\u002F*.yml` file in sorted order, parse each, and collect its `hooks.before_analyze` entries too — so a hook registered only in a per-extension file (e.g. the `feedback` extension at `.specify\u002Fextensions\u002Ffeedback\u002Ffeedback.yml`) is still discovered and runs.\n  - Merge all collected entries and dedupe by `(extension, command)` (first occurrence wins, so a hook declared in both files runs once).\n  - If a file is absent, no hooks are registered, or its YAML cannot be parsed\u002Fis invalid, skip that file silently and continue.\n- For every `optional: true` hook that is discovered but not executed this phase, emit one line so the skip is a visible decision: `Note: optional hook {extension}:{command} is registered but was not run (skipped).`\n- Filter out hooks where `enabled` is explicitly `false`. Treat hooks without an `enabled` field as enabled by default.\n- Do **not** interpret or evaluate hook `condition` expressions:\n  - If the hook has no `condition` field, or it is null\u002Fempty, treat the hook as executable\n  - If the hook defines a non-empty `condition`, skip the hook and leave condition evaluation to the HookExecutor implementation\n- For each executable hook, output the following based on its `optional` flag:\n  - **Optional hook** (`optional: true`):\n    ```\n    ## Extension Hooks\n\n    **Optional Pre-Hook**: {extension}\n    Command: `\u002F{command}`\n    Description: {description}\n\n    Prompt: {prompt}\n    To execute: `\u002F{command}`\n    ```\n  - **Mandatory hook** (`optional: false`):\n    ```\n    ## Extension Hooks\n\n    **Automatic Pre-Hook**: {extension}\n    Executing: `\u002F{command}`\n    EXECUTE_COMMAND: {command}\n\n    Wait for the result of the hook command before proceeding to the Goal.\n    ```\n\n## Goal\n\nIdentify inconsistencies, duplications, ambiguities, and underspecified items across the three core artifacts (`spec.md`, `plan.md`, `tasks.md`) before implementation. This command MUST run only after `\u002Fspeckit-tasks` has successfully produced a complete `tasks.md`.\n\n## Operating Constraints\n\n**STRICTLY READ-ONLY**: Do **not** modify any files. Output a structured analysis report. Offer an optional remediation plan (user must explicitly approve before any follow-up editing commands would be invoked manually).\n\n**Constitution Authority**: The project constitution (`.specify\u002Fmemory\u002Fconstitution.md`) is **non-negotiable** within this analysis scope. Constitution conflicts are automatically CRITICAL and require adjusting the spec, plan, or tasks — not diluting, reinterpreting, or silently ignoring the principle. Changing a principle itself must occur in a separate, explicit constitution update outside `\u002Fspeckit-analyze`.\n\n## Execution Steps\n\n### 1. Initialize Analysis Context\n\nRun `.specify\u002Fscripts\u002Fbash\u002Fcheck-prerequisites.sh --json --require-tasks --include-tasks` once from repo root and parse JSON for FEATURE_DIR and AVAILABLE_DOCS. Derive absolute paths:\n\n- SPEC = FEATURE_DIR\u002Fspec.md\n- PLAN = FEATURE_DIR\u002Fplan.md\n- TASKS = FEATURE_DIR\u002Ftasks.md\n\nAbort with an error message if any required file is missing (instruct the user to run missing prerequisite command).\nFor single quotes in args like \"I'm Groot\", use escape syntax: e.g 'I'\\''m Groot' (or double-quote if possible: \"I'm Groot\").\n\n### 2. Load Artifacts (Progressive Disclosure)\n\nLoad only the minimal necessary context from each artifact:\n\n**From spec.md:**\n\n- Overview\u002FContext\n- Functional Requirements\n- Success Criteria (measurable outcomes — e.g., performance, security, availability, user success, business impact)\n- User Stories\n- Edge Cases (if present)\n\n**From plan.md:**\n\n- Architecture\u002Fstack choices\n- Data Model references\n- Phases\n- Technical constraints\n\n**From tasks.md:**\n\n- Task IDs\n- Descriptions\n- Phase grouping\n- Parallel markers [P]\n- Referenced file paths\n\n**From constitution:**\n\n- Load `.specify\u002Fmemory\u002Fconstitution.md` for principle validation\n\n### 3. Build Semantic Models\n\nCreate internal representations (do not include raw artifacts in output):\n\n- **Requirements inventory**: For each Functional Requirement (FR-###) and Success Criterion (SC-###), record a stable key — the explicit FR-\u002FSC- identifier as primary key when present, optionally plus an imperative-phrase slug for readability (e.g., \"User can upload file\" → `user-can-upload-file`). Include only Success Criteria requiring buildable work (e.g., load-testing infrastructure, security audit tooling); exclude post-launch outcome metrics and business KPIs (e.g., \"Reduce support tickets by 50%\").\n- **User story\u002Faction inventory**: Discrete user actions with acceptance criteria\n- **Task coverage mapping**: Map each task to one or more requirements or stories (inference by keyword \u002F explicit reference patterns like IDs or key phrases)\n- **Constitution rule set**: Extract principle names and MUST\u002FSHOULD normative statements\n\n### 4. Detection Passes (Token-Efficient Analysis)\n\nFocus on high-signal findings. Limit to 50 findings total; aggregate remainder in overflow summary.\n\n#### A. Duplication Detection\n\n- Identify near-duplicate requirements\n- Mark lower-quality phrasing for consolidation\n\n#### B. Ambiguity Detection\n\n- Flag vague adjectives (fast, scalable, secure, intuitive, robust) lacking measurable criteria\n- Flag unresolved placeholders (TODO, TKTK, ???, `\u003Cplaceholder>`, etc.)\n\n#### C. Underspecification\n\n- Requirements with verbs but missing object or measurable outcome\n- User stories missing acceptance criteria alignment\n- Tasks referencing files or components not defined in spec\u002Fplan\n\n#### D. Constitution Alignment\n\n- Any requirement or plan element conflicting with a MUST principle\n- Missing mandated sections or quality gates from constitution\n\n#### E. Coverage Gaps\n\n- Requirements with zero associated tasks\n- Tasks with no mapped requirement\u002Fstory\n- Success Criteria requiring buildable work (performance, security, availability) not reflected in tasks\n\n#### F. Inconsistency\n\n- Terminology drift (same concept named differently across files)\n- Data entities referenced in plan but absent in spec (or vice versa)\n- Task ordering contradictions (e.g., integration tasks before foundational setup tasks without dependency note)\n- Conflicting requirements (e.g., one requires Next.js while other specifies Vue)\n\n#### G. Cross-Artifact Symbol Consistency (mechanical, FR-008)\n\nRun the **compiled, deterministic** symbol set-difference as a real command — do\n**not** eyeball it and do **not** hand-derive the set-difference:\n\n```bash\n.\u002Ffake.sh build -t SymbolCrossCheck\n```\n\n**Probe target availability first; skip-with-documented-notice when it is absent.**\n`SymbolCrossCheck` is a framework-repo-only governance target — **generated projects\ndo not ship it**, so the command fails there with `Unknown … target:\nSymbolCrossCheck`. Before invoking, probe whether the target resolves (e.g.\n`.\u002Ffake.sh build --list` \u002F a target-resolution check), mirroring how the\nevidence-graph step resolves the active feature from `.specify\u002Ffeature.json` and\nfails loudly only when nothing resolves. When `SymbolCrossCheck` resolves, run it and\nfold its output in. When it is **absent**, do **not** fail the analysis: record a\ndocumented skip notice in this report — `Symbol consistency (analyze pass G): skipped\n— SymbolCrossCheck target not available in this project; manual cross-check is\nnon-authoritative` — and continue. The skip is a visible decision, not a silent\nomission, and never blocks the invocation.\n\nThe target takes **no file arguments**: it resolves the active feature directory\n(the `DependencyReport` pattern), reads `plan.md`, `data-model.md`, and `tasks.md`\nfrom it, runs the `SymbolCrossCheck` analyzer in `FS.Skia.UI.Build`, **prints** the\nmarkdown, and **writes** it to `readiness\u002Fsymbol-cross-check.md`. Consume that output\nand fold its findings into this report. The analyzer extracts named symbols by kind —\n`Msg` cases, union\u002F`Screen` variants, entity record names (backtick-quoted PascalCase\ntokens on lines naming the kind), and `FR-`\u002F`SC-` IDs — and reports each symbol whose\npresence set is a **proper subset** of the three artifacts (present in some, missing\nfrom others). It renders as:\n\n```\n## Symbol consistency (analyze pass G)\n- msg-case ViewerKeyEventReceived — in {data-model, tasks}, missing from {plan}\n- sc-id SC-009 — in {plan}, missing from {data-model, tasks}\n```\n\nTreatment: report set-differences as findings at the appropriate severity for\nhuman judgment. A symbol present **only in design** (e.g. a start-state in\n`data-model.md` with no matching spec FR) is flagged `[design-only? human\njudgment]` and is **never hard-failed** — design-ahead-of-spec is a legitimate\nedge case (the cross-check is guidance, not a gate).\n\n### 5. Severity Assignment\n\nUse this heuristic to prioritize findings:\n\n- **CRITICAL**: Violates constitution MUST, missing core spec artifact, or requirement with zero coverage that blocks baseline functionality\n- **HIGH**: Duplicate or conflicting requirement, ambiguous security\u002Fperformance attribute, untestable acceptance criterion\n- **MEDIUM**: Terminology drift, missing non-functional task coverage, underspecified edge case\n- **LOW**: Style\u002Fwording improvements, minor redundancy not affecting execution order\n\n### 6. Produce Compact Analysis Report\n\nOutput a Markdown report (no file writes) with the following structure:\n\n## Specification Analysis Report\n\n| ID | Category | Severity | Location(s) | Summary | Recommendation |\n|----|----------|----------|-------------|---------|----------------|\n| A1 | Duplication | HIGH | spec.md:L120-134 | Two similar requirements ... | Merge phrasing; keep clearer version |\n\n(Add one row per finding; generate stable IDs prefixed by category initial.)\n\n**Coverage Summary Table:**\n\n| Requirement Key | Has Task? | Task IDs | Notes |\n|-----------------|-----------|----------|-------|\n\n**Constitution Alignment Issues:** (if any)\n\n**Unmapped Tasks:** (if any)\n\n**Metrics:**\n\n- Total Requirements\n- Total Tasks\n- Coverage % (requirements with >=1 task)\n- Ambiguity Count\n- Duplication Count\n- Critical Issues Count\n\n### 7. Provide Next Actions\n\nAt end of report, output a concise Next Actions block:\n\n- If CRITICAL issues exist: Recommend resolving before `\u002Fspeckit-implement`\n- If only LOW\u002FMEDIUM: User may proceed, but provide improvement suggestions\n- Provide explicit command suggestions: e.g., \"Run \u002Fspeckit-specify with refinement\", \"Run \u002Fspeckit-plan to adjust architecture\", \"Manually edit tasks.md to add coverage for 'performance-metrics'\"\n\n### 8. Offer Remediation\n\nAsk the user: \"Would you like me to suggest concrete remediation edits for the top N issues?\" (Do NOT apply them automatically.)\n\n### 9. Check for extension hooks\n\nAfter reporting, discover hooks across **all** extension files (multi-file discovery), not just the central file:\n- Read `.specify\u002Fextensions.yml` from the project root (if present) and collect entries under the `hooks.after_analyze` key.\n- Then enumerate every `.specify\u002Fextensions\u002F*\u002F*.yml` file in sorted order, parse each, and collect its `hooks.after_analyze` entries too — so a hook registered only in a per-extension file (e.g. the `feedback` extension at `.specify\u002Fextensions\u002Ffeedback\u002Ffeedback.yml`) is still discovered and runs on phase completion.\n- Merge all collected entries and dedupe by `(extension, command)` (first occurrence wins, so a hook declared in both files runs once).\n- **Hook execution precedence** (D1): when `settings.auto_execute_hooks: true` in `.specify\u002Fextensions.yml`, a **mandatory** hook (`optional: false`) **auto-runs** with no confirmation; an **optional** hook (`optional: true`) is **always surfaced** (\"To execute: `\u002F{command}`\") and is **never force-run** by `auto_execute_hooks`; a hook with a non-empty `condition` is **never** evaluated by this skill — evaluation is left to the executor and the notice reports the resolved decision. When `auto_execute_hooks: false`, even mandatory hooks are surfaced for confirmation.\n- **Effective-hooks notice** (D2): after the merge + dedup by `(extension, command)`, emit **one** consolidated notice for the phase so the operator never hand-reconciles files — the promoted feedback hook (`optional: false`) appears as `auto-run`, never as a surfaced optional:\n  ```\n  ## Effective hooks for analyze\n  - {extension}:{command} — auto-run        (mandatory; auto_execute_hooks=true)\n  - {extension}:{command} — surfaced        (optional)\n  - {extension}:{command} — skipped         (enabled: false)\n  - {extension}:{command} — condition-deferred\n  ```\n- If a file is absent, no hooks are registered, or its YAML cannot be parsed\u002Fis invalid, skip that file silently and continue.\n- For every `optional: true` hook that is discovered but not executed this phase, emit one line so the skip is a visible decision: `Note: optional hook {extension}:{command} is registered but was not run (skipped).`\n- Filter out hooks where `enabled` is explicitly `false`. Treat hooks without an `enabled` field as enabled by default.\n- Do **not** interpret or evaluate hook `condition` expressions:\n  - If the hook has no `condition` field, or it is null\u002Fempty, treat the hook as executable\n  - If the hook defines a non-empty `condition`, skip the hook and leave condition evaluation to the HookExecutor implementation\n- For each executable hook, output the following based on its `optional` flag:\n  - **Optional hook** (`optional: true`):\n    ```\n    ## Extension Hooks\n\n    **Optional Hook**: {extension}\n    Command: `\u002F{command}`\n    Description: {description}\n\n    Prompt: {prompt}\n    To execute: `\u002F{command}`\n    ```\n  - **Mandatory hook** (`optional: false`):\n    ```\n    ## Extension Hooks\n\n    **Automatic Hook**: {extension}\n    Executing: `\u002F{command}`\n    EXECUTE_COMMAND: {command}\n    ```\n\n## Operating Principles\n\n### Context Efficiency\n\n- **Minimal high-signal tokens**: Focus on actionable findings, not exhaustive documentation\n- **Progressive disclosure**: Load artifacts incrementally; don't dump all content into analysis\n- **Token-efficient output**: Limit findings table to 50 rows; summarize overflow\n- **Deterministic results**: Rerunning without changes should produce consistent IDs and counts\n\n### Analysis Guidelines\n\n- **NEVER modify files** (this is read-only analysis)\n- **NEVER hallucinate missing sections** (if absent, report them accurately)\n- **Prioritize constitution violations** (these are always CRITICAL)\n- **Use examples over exhaustive rules** (cite specific instances, not generic patterns)\n- **Report zero issues gracefully** (emit success report with coverage statistics)\n\n## Context\n\n$ARGUMENTS\n","## User Input\n\n```text\n$ARGUMENTS\n```\n\nYou **MUST** consider the user input before proceeding (if not empty).\n\n## Pre-Execution Checks\n\n**Check for extension hooks (before analysis)**:\n- Discover hooks across **all** extension files (multi-file discovery), not just the central file:\n  - Read `.specify\u002Fextensions.yml` from the project root (if present) and collect entries under the `hooks.before_analyze` key.\n  - Then enumerate every `.specify\u002Fextensions\u002F*\u002F*.yml` file in sorted order, parse each, and collect its `hooks.before_analyze` entries too — so a hook registered only in a per-extension file (e.g. the `feedback` extension at `.specify\u002Fextensions\u002Ffeedback\u002Ffeedback.yml`) is still discovered and runs.\n  - Merge all collected entries and dedupe by `(extension, command)` (first occurrence wins, so a hook declared in both files runs once).\n  - If a file is absent, no hooks are registered, or its YAML cannot be parsed\u002Fis invalid, skip that file silently and continue.\n- For every `optional: true` hook that is discovered but not executed this phase, emit one line so the skip is a visible decision: `Note: optional hook {extension}:{command} is registered but was not run (skipped).`\n- Filter out hooks where `enabled` is explicitly `false`. Treat hooks without an `enabled` field as enabled by default.\n- Do **not** interpret or evaluate hook `condition` expressions:\n  - If the hook has no `condition` field, or it is null\u002Fempty, treat the hook as executable\n  - If the hook defines a non-empty `condition`, skip the hook and leave condition evaluation to the HookExecutor implementation\n- For each executable hook, output the following based on its `optional` flag:\n  - **Optional hook** (`optional: true`):\n    ```\n    ## Extension Hooks\n\n    **Optional Pre-Hook**: {extension}\n    Command: `\u002F{command}`\n    Description: {description}\n\n    Prompt: {prompt}\n    To execute: `\u002F{command}`\n    ```\n  - **Mandatory hook** (`optional: false`):\n    ```\n    ## Extension Hooks\n\n    **Automatic Pre-Hook**: {extension}\n    Executing: `\u002F{command}`\n    EXECUTE_COMMAND: {command}\n\n    Wait for the result of the hook command before proceeding to the Goal.\n    ```\n\n## Goal\n\nIdentify inconsistencies, duplications, ambiguities, and underspecified items across the three core artifacts (`spec.md`, `plan.md`, `tasks.md`) before implementation. This command MUST run only after `\u002Fspeckit-tasks` has successfully produced a complete `tasks.md`.\n\n## Operating Constraints\n\n**STRICTLY READ-ONLY**: Do **not** modify any files. Output a structured analysis report. Offer an optional remediation plan (user must explicitly approve before any follow-up editing commands would be invoked manually).\n\n**Constitution Authority**: The project constitution (`.specify\u002Fmemory\u002Fconstitution.md`) is **non-negotiable** within this analysis scope. Constitution conflicts are automatically CRITICAL and require adjusting the spec, plan, or tasks — not diluting, reinterpreting, or silently ignoring the principle. Changing a principle itself must occur in a separate, explicit constitution update outside `\u002Fspeckit-analyze`.\n\n## Execution Steps\n\n### 1. Initialize Analysis Context\n\nRun `.specify\u002Fscripts\u002Fbash\u002Fcheck-prerequisites.sh --json --require-tasks --include-tasks` once from repo root and parse JSON for FEATURE_DIR and AVAILABLE_DOCS. Derive absolute paths:\n\n- SPEC = FEATURE_DIR\u002Fspec.md\n- PLAN = FEATURE_DIR\u002Fplan.md\n- TASKS = FEATURE_DIR\u002Ftasks.md\n\nAbort with an error message if any required file is missing (instruct the user to run missing prerequisite command).\nFor single quotes in args like \"I'm Groot\", use escape syntax: e.g 'I'\\''m Groot' (or double-quote if possible: \"I'm Groot\").\n\n### 2. Load Artifacts (Progressive Disclosure)\n\nLoad only the minimal necessary context from each artifact:\n\n**From spec.md:**\n\n- Overview\u002FContext\n- Functional Requirements\n- Success Criteria (measurable outcomes — e.g., performance, security, availability, user success, business impact)\n- User Stories\n- Edge Cases (if present)\n\n**From plan.md:**\n\n- Architecture\u002Fstack choices\n- Data Model references\n- Phases\n- Technical constraints\n\n**From tasks.md:**\n\n- Task IDs\n- Descriptions\n- Phase grouping\n- Parallel markers [P]\n- Referenced file paths\n\n**From constitution:**\n\n- Load `.specify\u002Fmemory\u002Fconstitution.md` for principle validation\n\n### 3. Build Semantic Models\n\nCreate internal representations (do not include raw artifacts in output):\n\n- **Requirements inventory**: For each Functional Requirement (FR-###) and Success Criterion (SC-###), record a stable key — the explicit FR-\u002FSC- identifier as primary key when present, optionally plus an imperative-phrase slug for readability (e.g., \"User can upload file\" → `user-can-upload-file`). Include only Success Criteria requiring buildable work (e.g., load-testing infrastructure, security audit tooling); exclude post-launch outcome metrics and business KPIs (e.g., \"Reduce support tickets by 50%\").\n- **User story\u002Faction inventory**: Discrete user actions with acceptance criteria\n- **Task coverage mapping**: Map each task to one or more requirements or stories (inference by keyword \u002F explicit reference patterns like IDs or key phrases)\n- **Constitution rule set**: Extract principle names and MUST\u002FSHOULD normative statements\n\n### 4. Detection Passes (Token-Efficient Analysis)\n\nFocus on high-signal findings. Limit to 50 findings total; aggregate remainder in overflow summary.\n\n#### A. Duplication Detection\n\n- Identify near-duplicate requirements\n- Mark lower-quality phrasing for consolidation\n\n#### B. Ambiguity Detection\n\n- Flag vague adjectives (fast, scalable, secure, intuitive, robust) lacking measurable criteria\n- Flag unresolved placeholders (TODO, TKTK, ???, `\u003Cplaceholder>`, etc.)\n\n#### C. Underspecification\n\n- Requirements with verbs but missing object or measurable outcome\n- User stories missing acceptance criteria alignment\n- Tasks referencing files or components not defined in spec\u002Fplan\n\n#### D. Constitution Alignment\n\n- Any requirement or plan element conflicting with a MUST principle\n- Missing mandated sections or quality gates from constitution\n\n#### E. Coverage Gaps\n\n- Requirements with zero associated tasks\n- Tasks with no mapped requirement\u002Fstory\n- Success Criteria requiring buildable work (performance, security, availability) not reflected in tasks\n\n#### F. Inconsistency\n\n- Terminology drift (same concept named differently across files)\n- Data entities referenced in plan but absent in spec (or vice versa)\n- Task ordering contradictions (e.g., integration tasks before foundational setup tasks without dependency note)\n- Conflicting requirements (e.g., one requires Next.js while other specifies Vue)\n\n#### G. Cross-Artifact Symbol Consistency (mechanical, FR-008)\n\nRun the **compiled, deterministic** symbol set-difference as a real command — do\n**not** eyeball it and do **not** hand-derive the set-difference:\n\n```bash\n.\u002Ffake.sh build -t SymbolCrossCheck\n```\n\n**Probe target availability first; skip-with-documented-notice when it is absent.**\n`SymbolCrossCheck` is a framework-repo-only governance target — **generated projects\ndo not ship it**, so the command fails there with `Unknown … target:\nSymbolCrossCheck`. Before invoking, probe whether the target resolves (e.g.\n`.\u002Ffake.sh build --list` \u002F a target-resolution check), mirroring how the\nevidence-graph step resolves the active feature from `.specify\u002Ffeature.json` and\nfails loudly only when nothing resolves. When `SymbolCrossCheck` resolves, run it and\nfold its output in. When it is **absent**, do **not** fail the analysis: record a\ndocumented skip notice in this report — `Symbol consistency (analyze pass G): skipped\n— SymbolCrossCheck target not available in this project; manual cross-check is\nnon-authoritative` — and continue. The skip is a visible decision, not a silent\nomission, and never blocks the invocation.\n\nThe target takes **no file arguments**: it resolves the active feature directory\n(the `DependencyReport` pattern), reads `plan.md`, `data-model.md`, and `tasks.md`\nfrom it, runs the `SymbolCrossCheck` analyzer in `FS.Skia.UI.Build`, **prints** the\nmarkdown, and **writes** it to `readiness\u002Fsymbol-cross-check.md`. Consume that output\nand fold its findings into this report. The analyzer extracts named symbols by kind —\n`Msg` cases, union\u002F`Screen` variants, entity record names (backtick-quoted PascalCase\ntokens on lines naming the kind), and `FR-`\u002F`SC-` IDs — and reports each symbol whose\npresence set is a **proper subset** of the three artifacts (present in some, missing\nfrom others). It renders as:\n\n```\n## Symbol consistency (analyze pass G)\n- msg-case ViewerKeyEventReceived — in {data-model, tasks}, missing from {plan}\n- sc-id SC-009 — in {plan}, missing from {data-model, tasks}\n```\n\nTreatment: report set-differences as findings at the appropriate severity for\nhuman judgment. A symbol present **only in design** (e.g. a start-state in\n`data-model.md` with no matching spec FR) is flagged `[design-only? human\njudgment]` and is **never hard-failed** — design-ahead-of-spec is a legitimate\nedge case (the cross-check is guidance, not a gate).\n\n### 5. Severity Assignment\n\nUse this heuristic to prioritize findings:\n\n- **CRITICAL**: Violates constitution MUST, missing core spec artifact, or requirement with zero coverage that blocks baseline functionality\n- **HIGH**: Duplicate or conflicting requirement, ambiguous security\u002Fperformance attribute, untestable acceptance criterion\n- **MEDIUM**: Terminology drift, missing non-functional task coverage, underspecified edge case\n- **LOW**: Style\u002Fwording improvements, minor redundancy not affecting execution order\n\n### 6. Produce Compact Analysis Report\n\nOutput a Markdown report (no file writes) with the following structure:\n\n## Specification Analysis Report\n\n| ID | Category | Severity | Location(s) | Summary | Recommendation |\n|----|----------|----------|-------------|---------|----------------|\n| A1 | Duplication | HIGH | spec.md:L120-134 | Two similar requirements ... | Merge phrasing; keep clearer version |\n\n(Add one row per finding; generate stable IDs prefixed by category initial.)\n\n**Coverage Summary Table:**\n\n| Requirement Key | Has Task? | Task IDs | Notes |\n|-----------------|-----------|----------|-------|\n\n**Constitution Alignment Issues:** (if any)\n\n**Unmapped Tasks:** (if any)\n\n**Metrics:**\n\n- Total Requirements\n- Total Tasks\n- Coverage % (requirements with >=1 task)\n- Ambiguity Count\n- Duplication Count\n- Critical Issues Count\n\n### 7. Provide Next Actions\n\nAt end of report, output a concise Next Actions block:\n\n- If CRITICAL issues exist: Recommend resolving before `\u002Fspeckit-implement`\n- If only LOW\u002FMEDIUM: User may proceed, but provide improvement suggestions\n- Provide explicit command suggestions: e.g., \"Run \u002Fspeckit-specify with refinement\", \"Run \u002Fspeckit-plan to adjust architecture\", \"Manually edit tasks.md to add coverage for 'performance-metrics'\"\n\n### 8. Offer Remediation\n\nAsk the user: \"Would you like me to suggest concrete remediation edits for the top N issues?\" (Do NOT apply them automatically.)\n\n### 9. Check for extension hooks\n\nAfter reporting, discover hooks across **all** extension files (multi-file discovery), not just the central file:\n- Read `.specify\u002Fextensions.yml` from the project root (if present) and collect entries under the `hooks.after_analyze` key.\n- Then enumerate every `.specify\u002Fextensions\u002F*\u002F*.yml` file in sorted order, parse each, and collect its `hooks.after_analyze` entries too — so a hook registered only in a per-extension file (e.g. the `feedback` extension at `.specify\u002Fextensions\u002Ffeedback\u002Ffeedback.yml`) is still discovered and runs on phase completion.\n- Merge all collected entries and dedupe by `(extension, command)` (first occurrence wins, so a hook declared in both files runs once).\n- **Hook execution precedence** (D1): when `settings.auto_execute_hooks: true` in `.specify\u002Fextensions.yml`, a **mandatory** hook (`optional: false`) **auto-runs** with no confirmation; an **optional** hook (`optional: true`) is **always surfaced** (\"To execute: `\u002F{command}`\") and is **never force-run** by `auto_execute_hooks`; a hook with a non-empty `condition` is **never** evaluated by this skill — evaluation is left to the executor and the notice reports the resolved decision. When `auto_execute_hooks: false`, even mandatory hooks are surfaced for confirmation.\n- **Effective-hooks notice** (D2): after the merge + dedup by `(extension, command)`, emit **one** consolidated notice for the phase so the operator never hand-reconciles files — the promoted feedback hook (`optional: false`) appears as `auto-run`, never as a surfaced optional:\n  ```\n  ## Effective hooks for analyze\n  - {extension}:{command} — auto-run        (mandatory; auto_execute_hooks=true)\n  - {extension}:{command} — surfaced        (optional)\n  - {extension}:{command} — skipped         (enabled: false)\n  - {extension}:{command} — condition-deferred\n  ```\n- If a file is absent, no hooks are registered, or its YAML cannot be parsed\u002Fis invalid, skip that file silently and continue.\n- For every `optional: true` hook that is discovered but not executed this phase, emit one line so the skip is a visible decision: `Note: optional hook {extension}:{command} is registered but was not run (skipped).`\n- Filter out hooks where `enabled` is explicitly `false`. Treat hooks without an `enabled` field as enabled by default.\n- Do **not** interpret or evaluate hook `condition` expressions:\n  - If the hook has no `condition` field, or it is null\u002Fempty, treat the hook as executable\n  - If the hook defines a non-empty `condition`, skip the hook and leave condition evaluation to the HookExecutor implementation\n- For each executable hook, output the following based on its `optional` flag:\n  - **Optional hook** (`optional: true`):\n    ```\n    ## Extension Hooks\n\n    **Optional Hook**: {extension}\n    Command: `\u002F{command}`\n    Description: {description}\n\n    Prompt: {prompt}\n    To execute: `\u002F{command}`\n    ```\n  - **Mandatory hook** (`optional: false`):\n    ```\n    ## Extension Hooks\n\n    **Automatic Hook**: {extension}\n    Executing: `\u002F{command}`\n    EXECUTE_COMMAND: {command}\n    ```\n\n## Operating Principles\n\n### Context Efficiency\n\n- **Minimal high-signal tokens**: Focus on actionable findings, not exhaustive documentation\n- **Progressive disclosure**: Load artifacts incrementally; don't dump all content into analysis\n- **Token-efficient output**: Limit findings table to 50 rows; summarize overflow\n- **Deterministic results**: Rerunning without changes should produce consistent IDs and counts\n\n### Analysis Guidelines\n\n- **NEVER modify files** (this is read-only analysis)\n- **NEVER hallucinate missing sections** (if absent, report them accurately)\n- **Prioritize constitution violations** (these are always CRITICAL)\n- **Use examples over exhaustive rules** (cite specific instances, not generic patterns)\n- **Report zero issues gracefully** (emit success report with coverage statistics)\n\n## Context\n\n$ARGUMENTS\n",{"name":5,"metadata":23,"description":7,"compatibility":26},{"author":24,"source":25},"github-spec-kit","templates\u002Fcommands\u002Fanalyze.md","Requires spec-kit project structure with .specify\u002F directory","main","f943406829a9218b2882e09eb88d4ddb539c5e72",".agents\u002Fskills\u002Fspeckit-analyze",0,"https:\u002F\u002Fgithub.com\u002FEHotwagner\u002FFS-Skia-UI","https:\u002F\u002Fgithub.com\u002FEHotwagner","2026-06-16 16:16:52",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add EHotwagner\u002FFS-Skia-UI --skill speckit-analyze",{"tool":40,"command":41},"bunx","bunx skills add EHotwagner\u002FFS-Skia-UI --skill speckit-analyze",{"tool":43,"command":44},"pnpm","pnpm dlx skills add EHotwagner\u002FFS-Skia-UI --skill speckit-analyze","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FEHotwagner\u002FFS-Skia-UI\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fspeckit-analyze\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":18},"01M72SGYR4T02T1HTS175E0V86","fs-skia-ui-widgets","Generated product guidance for Skia-rendered FS.Skia.UI Controls, rich text, chart controls, graph controls, DataGrid, and custom wrappers.","https:\u002F\u002Fgithub.com\u002FEHotwagner\u002FFS-Skia-UI\u002Fblob\u002Fmain\u002Ftemplate\u002Fproduct-skills\u002Ffs-skia-ui-widgets\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":18},"01M72SGVZJR1B117QK7TCC6E0J","fs-skia-testing","Assert generated-product expectations and evidence in a governed FS.Skia.UI product.","https:\u002F\u002Fgithub.com\u002FEHotwagner\u002FFS-Skia-UI\u002Fblob\u002Fmain\u002Ftemplate\u002Fproduct-skills\u002Ffs-skia-testing\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M72SGTC5HZYEVVVZT4X51AZ3","fs-skia-skiaviewer","Wire a generated FS.Skia.UI product to the desktop viewer host.","https:\u002F\u002Fgithub.com\u002FEHotwagner\u002FFS-Skia-UI\u002Fblob\u002Fmain\u002Ftemplate\u002Fproduct-skills\u002Ffs-skia-skiaviewer\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M72SGS47RPYPC9JTC39CC6EF","fs-skia-scene","Build pure scene descriptions in a generated FS.Skia.UI product.","https:\u002F\u002Fgithub.com\u002FEHotwagner\u002FFS-Skia-UI\u002Fblob\u002Fmain\u002Ftemplate\u002Fproduct-skills\u002Ffs-skia-scene\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M72SGQF4G76C4NGSF69KZRRF","fs-skia-keyboard-input","Map keyboard input to product commands in a generated FS.Skia.UI product.","https:\u002F\u002Fgithub.com\u002FEHotwagner\u002FFS-Skia-UI\u002Fblob\u002Fmain\u002Ftemplate\u002Fproduct-skills\u002Ffs-skia-keyboard-input\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M72SGNJP3PMSS2VRP98G7Z42","fs-skia-elmish","Drive a generated FS.Skia.UI product through the pure Elmish adapter.","https:\u002F\u002Fgithub.com\u002FEHotwagner\u002FFS-Skia-UI\u002Fblob\u002Fmain\u002Ftemplate\u002Fproduct-skills\u002Ffs-skia-elmish\u002FSKILL.md",[],[]]