[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75DZ1H0T6CTZ91AG8WSZNP2":3,"skill-same:01M75DZ1H0T6CTZ91AG8WSZNP2":59},{"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":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":48},"01M75DZ1H0T6CTZ91AG8WSZNP2","sdd-verify",null,"Trigger: SDD verification phase, verify change. Execute tests and prove implementation matches specs, design, and tasks.","AdrichDev\u002Fgru_orchestrator","AdrichDev","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F172129260?v=4","01M75DR1Z03617FFA846AG5JJ6","Adrián Chozas","01M75DR1ZMXV62W49NBFHAMQBT",0,"MIT","https:\u002F\u002Fgithub.com\u002FAdrichDev\u002Fgru_orchestrator\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fsdd-verify\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: sdd-verify\ndescription: \"Trigger: SDD verification phase, verify change. Execute tests and prove implementation matches specs, design, and tasks.\"\ndisable-model-invocation: true\nuser-invocable: false\nlicense: MIT\nmetadata:\n  author: gentleman-programming\n  version: \"3.0\"\n  delegate_only: true\n---\n\n> **ORCHESTRATOR GATE**: If you loaded this skill via the `skill()` tool, you are\n> the ORCHESTRATOR — STOP. Do NOT execute these instructions inline. Delegate to\n> the dedicated `sdd-verify` sub-agent using your platform's delegation primitive\n> (e.g., `task(...)`, sub-agent invocation, etc.). This skill is for EXECUTORS\n> only.\n\n## Executor Override\n\nIf you ARE the `sdd-verify` sub-agent (NOT the orchestrator), the gate above does NOT apply to you. Continue with the phase work below. Do NOT delegate. Do NOT call the Skill tool. You are the executor — execute.\n\n## Language Domain Contract\n\nGenerated technical artifacts default to English. Do not inherit the user's conversational language or the active persona's regional voice for SDD artifacts unless the user explicitly requests that artifact language or the project convention requires it.\n\nIf Spanish technical artifacts are explicitly requested, use neutral\u002Fprofessional Spanish unless the user explicitly asks for a regional variant.\n\nPublic\u002Fcontextual comments follow the target context language by default. Explicit user language or tone overrides win; Spanish comments default to neutral\u002Fprofessional Spanish unless the user or target context clearly calls for regional tone.\n\n## Activation Contract\n\nRun when the orchestrator launches verification for an SDD change. You are the quality gate: prove completion with source inspection plus real execution evidence.\n\nThe orchestrator should provide structured status from `skills\u002F_shared\u002Fsdd-status-contract.md`. Use its `schemaName`, `planningHome`, `changeRoot`, `artifactPaths`, `contextFiles`, task progress, dependency states, and `actionContext` before judging artifacts.\n\n## Hard Rules\n\n- Read all available status `contextFiles` before judging implementation. Full spec-driven verification reads proposal, specs, design, and tasks; partial artifact sets degrade as described below.\n- Execute relevant tests; static analysis alone is never verification.\n- A spec scenario is compliant only when a covering test passed at runtime.\n- Compare specs first, design second, task completion third.\n- Do not fix issues; report them for the orchestrator\u002Fuser.\n- Persist `verify-report` according to mode: Engram, openspec file, hybrid both, or inline-only for `none`.\n- If Strict TDD is active, load `strict-tdd-verify.md` from this skill directory; if inactive, never load it.\n- Return the Section D envelope from `..\u002F_shared\u002Fsdd-phase-common.md`.\n\n## Decision Gates\n\n| Condition | Action |\n|---|---|\n| Orchestrator says `STRICT TDD MODE IS ACTIVE` | Treat as authoritative. |\n| Cached\u002Fconfig `strict_tdd: true` and runner exists | Strict TDD verify; load module. |\n| Strict TDD false or no runner | Standard verify; skip TDD checks. |\n| `actionContext.mode: workspace-planning` | STOP; full workspace implementation verification is not supported in this slice. |\n| Only tasks artifact exists | Verify task completion only; skip spec\u002Fdesign correctness and record skipped checks. |\n| Tasks + specs exist | Verify completeness and correctness; skip design coherence and record skipped checks. |\n| Proposal\u002Fspecs\u002Fdesign\u002Ftasks exist | Verify all dimensions. |\n| Task incomplete | CRITICAL for core task, WARNING for cleanup task. |\n| Test command exits non-zero | CRITICAL. |\n| Spec scenario has no passing covering test | CRITICAL `UNTESTED` or `FAILING`. |\n| Design deviation exists | WARNING unless it breaks a spec. |\n\n## Execution Steps\n\n1. Load relevant skills via shared SDD Section A.\n2. Retrieve artifacts via shared Section B for the active persistence mode, or read the concrete `contextFiles` from structured status.\n3. Resolve testing\u002FTDD mode from cached capabilities, config, or project files.\n4. Count completed and incomplete tasks. Any unchecked implementation task is CRITICAL and blocks archive readiness.\n5. If specs exist, map each spec requirement\u002Fscenario to implementation evidence and tests.\n6. If design exists, check design decisions against changed code. If design is missing, skip design coherence and record why.\n7. Run test, build\u002Ftype-check, and coverage commands when available. For full spec verification, preserve gentle-ai's stricter runtime evidence: source inspection alone does not prove spec scenario compliance.\n8. Build the behavioral compliance matrix from actual test results when specs\u002Fscenarios exist.\n9. Persist and return the verification report, including skipped dimensions for missing artifacts.\n\n## Output Contract\n\nReturn `## Verification Report` with change, mode, completeness table, build\u002Ftests\u002Fcoverage evidence, spec compliance matrix, correctness table, design coherence table, issues grouped as CRITICAL\u002FWARNING\u002FSUGGESTION, and final verdict `PASS`, `PASS WITH WARNINGS`, or `FAIL`.\n\n## Graceful Artifact Handling\n\n- **Tasks only**: verify objective task completion only. Do not claim spec correctness or design coherence. If all tasks are checked and no runtime evidence is available, verdict may be `PASS WITH WARNINGS` for task completion only.\n- **Tasks + specs**: verify task completeness and requirement\u002Fscenario correctness. Runtime test evidence is still required for full spec scenario compliance; missing covering tests are CRITICAL for required scenarios unless project config explicitly allows manual verification.\n- **Full artifacts**: verify completeness, correctness, and coherence.\n- **Unchecked tasks**: always remain CRITICAL, even when other artifacts are missing or warnings-only.\n\n## References\n\n- [references\u002Freport-format.md](references\u002Freport-format.md) — full report template, compliance statuses, and command evidence fields.\n- [strict-tdd-verify.md](strict-tdd-verify.md) — load only when Strict TDD is active.\n- `..\u002F_shared\u002Fsdd-phase-common.md` — skill loading, retrieval, persistence, and return envelope.\n","> **ORCHESTRATOR GATE**: If you loaded this skill via the `skill()` tool, you are\n> the ORCHESTRATOR — STOP. Do NOT execute these instructions inline. Delegate to\n> the dedicated `sdd-verify` sub-agent using your platform's delegation primitive\n> (e.g., `task(...)`, sub-agent invocation, etc.). This skill is for EXECUTORS\n> only.\n\n## Executor Override\n\nIf you ARE the `sdd-verify` sub-agent (NOT the orchestrator), the gate above does NOT apply to you. Continue with the phase work below. Do NOT delegate. Do NOT call the Skill tool. You are the executor — execute.\n\n## Language Domain Contract\n\nGenerated technical artifacts default to English. Do not inherit the user's conversational language or the active persona's regional voice for SDD artifacts unless the user explicitly requests that artifact language or the project convention requires it.\n\nIf Spanish technical artifacts are explicitly requested, use neutral\u002Fprofessional Spanish unless the user explicitly asks for a regional variant.\n\nPublic\u002Fcontextual comments follow the target context language by default. Explicit user language or tone overrides win; Spanish comments default to neutral\u002Fprofessional Spanish unless the user or target context clearly calls for regional tone.\n\n## Activation Contract\n\nRun when the orchestrator launches verification for an SDD change. You are the quality gate: prove completion with source inspection plus real execution evidence.\n\nThe orchestrator should provide structured status from `skills\u002F_shared\u002Fsdd-status-contract.md`. Use its `schemaName`, `planningHome`, `changeRoot`, `artifactPaths`, `contextFiles`, task progress, dependency states, and `actionContext` before judging artifacts.\n\n## Hard Rules\n\n- Read all available status `contextFiles` before judging implementation. Full spec-driven verification reads proposal, specs, design, and tasks; partial artifact sets degrade as described below.\n- Execute relevant tests; static analysis alone is never verification.\n- A spec scenario is compliant only when a covering test passed at runtime.\n- Compare specs first, design second, task completion third.\n- Do not fix issues; report them for the orchestrator\u002Fuser.\n- Persist `verify-report` according to mode: Engram, openspec file, hybrid both, or inline-only for `none`.\n- If Strict TDD is active, load `strict-tdd-verify.md` from this skill directory; if inactive, never load it.\n- Return the Section D envelope from `..\u002F_shared\u002Fsdd-phase-common.md`.\n\n## Decision Gates\n\n| Condition | Action |\n|---|---|\n| Orchestrator says `STRICT TDD MODE IS ACTIVE` | Treat as authoritative. |\n| Cached\u002Fconfig `strict_tdd: true` and runner exists | Strict TDD verify; load module. |\n| Strict TDD false or no runner | Standard verify; skip TDD checks. |\n| `actionContext.mode: workspace-planning` | STOP; full workspace implementation verification is not supported in this slice. |\n| Only tasks artifact exists | Verify task completion only; skip spec\u002Fdesign correctness and record skipped checks. |\n| Tasks + specs exist | Verify completeness and correctness; skip design coherence and record skipped checks. |\n| Proposal\u002Fspecs\u002Fdesign\u002Ftasks exist | Verify all dimensions. |\n| Task incomplete | CRITICAL for core task, WARNING for cleanup task. |\n| Test command exits non-zero | CRITICAL. |\n| Spec scenario has no passing covering test | CRITICAL `UNTESTED` or `FAILING`. |\n| Design deviation exists | WARNING unless it breaks a spec. |\n\n## Execution Steps\n\n1. Load relevant skills via shared SDD Section A.\n2. Retrieve artifacts via shared Section B for the active persistence mode, or read the concrete `contextFiles` from structured status.\n3. Resolve testing\u002FTDD mode from cached capabilities, config, or project files.\n4. Count completed and incomplete tasks. Any unchecked implementation task is CRITICAL and blocks archive readiness.\n5. If specs exist, map each spec requirement\u002Fscenario to implementation evidence and tests.\n6. If design exists, check design decisions against changed code. If design is missing, skip design coherence and record why.\n7. Run test, build\u002Ftype-check, and coverage commands when available. For full spec verification, preserve gentle-ai's stricter runtime evidence: source inspection alone does not prove spec scenario compliance.\n8. Build the behavioral compliance matrix from actual test results when specs\u002Fscenarios exist.\n9. Persist and return the verification report, including skipped dimensions for missing artifacts.\n\n## Output Contract\n\nReturn `## Verification Report` with change, mode, completeness table, build\u002Ftests\u002Fcoverage evidence, spec compliance matrix, correctness table, design coherence table, issues grouped as CRITICAL\u002FWARNING\u002FSUGGESTION, and final verdict `PASS`, `PASS WITH WARNINGS`, or `FAIL`.\n\n## Graceful Artifact Handling\n\n- **Tasks only**: verify objective task completion only. Do not claim spec correctness or design coherence. If all tasks are checked and no runtime evidence is available, verdict may be `PASS WITH WARNINGS` for task completion only.\n- **Tasks + specs**: verify task completeness and requirement\u002Fscenario correctness. Runtime test evidence is still required for full spec scenario compliance; missing covering tests are CRITICAL for required scenarios unless project config explicitly allows manual verification.\n- **Full artifacts**: verify completeness, correctness, and coherence.\n- **Unchecked tasks**: always remain CRITICAL, even when other artifacts are missing or warnings-only.\n\n## References\n\n- [references\u002Freport-format.md](references\u002Freport-format.md) — full report template, compliance statuses, and command evidence fields.\n- [strict-tdd-verify.md](strict-tdd-verify.md) — load only when Strict TDD is active.\n- `..\u002F_shared\u002Fsdd-phase-common.md` — skill loading, retrieval, persistence, and return envelope.\n",{"name":5,"license":15,"metadata":24,"description":7,"user-invocable":20,"disable-model-invocation":27},{"author":25,"version":26,"delegate_only":27},"gentleman-programming","3.0",true,"main","6745e47ba2ea20f71dce9a8303c332ef63ef43b6",".claude\u002Fskills\u002Fsdd-verify","https:\u002F\u002Fgithub.com\u002FAdrichDev\u002Fgru_orchestrator","https:\u002F\u002Fgithub.com\u002FAdrichDev","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fadrichv\u002F","Software Junior Developer en continua formación y aprendizaje. Además , Trabajador social.\r\nIntentaré ir subiendo cositas!! \r\nFeliz día!!","2026-11-15 04:14:37",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":27},[38,41,44],{"tool":39,"command":40},"npx","npx skills add AdrichDev\u002Fgru_orchestrator --skill sdd-verify",{"tool":42,"command":43},"bunx","bunx skills add AdrichDev\u002Fgru_orchestrator --skill sdd-verify",{"tool":45,"command":46},"pnpm","pnpm dlx skills add AdrichDev\u002Fgru_orchestrator --skill sdd-verify","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAdrichDev\u002Fgru_orchestrator\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fsdd-verify\u002FSKILL.md",[49,55],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Freport-format.md","REFERENCE","参考文档",1750,"https:\u002F\u002Fgithub.com\u002FAdrichDev\u002Fgru_orchestrator\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fsdd-verify\u002Freferences\u002Freport-format.md",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"strict-tdd-verify.md",12876,"https:\u002F\u002Fgithub.com\u002FAdrichDev\u002Fgru_orchestrator\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fsdd-verify\u002Fstrict-tdd-verify.md",[60,67,72,80,87,94],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M75ED2J1WS4B52JV2Q0R01CB","invocable-skill","Run a security audit on the specified target. Use when asked to audit, scan, or assess security posture.","https:\u002F\u002Fgithub.com\u002FAdrichDev\u002Fgru_orchestrator\u002Fblob\u002Fmain\u002Fpackages\u002Fkernel\u002Fsrc\u002Fadapters\u002F__tests__\u002Fmock-ac-root\u002Fskills\u002Finvocable-skill\u002FSKILL.md",[],[],{"skillNo":68,"name":62,"nameZh":6,"description":63,"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},"01M75ECRCQFK3WY7Q990S3ZANF","https:\u002F\u002Fgithub.com\u002FAdrichDev\u002Fgru_orchestrator\u002Fblob\u002Fmain\u002Fpackages\u002Fkernel\u002Fsrc\u002Fadapters\u002F__tests__\u002Ffixtures-ac\u002Finvocable-skill\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":76,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M75ECJTFT8NZXFX0M95XHBGJ","work-unit-commits","Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FAdrichDev\u002Fgru_orchestrator\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fwork-unit-commits\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M75ECHC0CRV7MCB19WVAPQZN","skill-registry","Trigger: update skills, skill registry, actualizar skills, after skill changes. Index available skills by trigger and path.","https:\u002F\u002Fgithub.com\u002FAdrichDev\u002Fgru_orchestrator\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fskill-registry\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":76,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M75ECFSPSZCFMA3BK74SN2M7","skill-improver","Trigger: improve skills, audit skills, refactor skills, skill quality. Audit and upgrade existing LLM-first skills.","https:\u002F\u002Fgithub.com\u002FAdrichDev\u002Fgru_orchestrator\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fskill-improver\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":76,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M75ECE874149EMN8ZEEMSAPM","skill-creator","Trigger: new skills, agent instructions, documenting AI usage patterns. Create LLM-first skills with valid frontmatter.","https:\u002F\u002Fgithub.com\u002FAdrichDev\u002Fgru_orchestrator\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fskill-creator\u002FSKILL.md",[],[]]