[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M736K6PQVENY9V59GXYVMVBQ":3,"skill-same:01M736K6PQVENY9V59GXYVMVBQ":50},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M736K6PQVENY9V59GXYVMVBQ","execute",null,"Execute the implementation plan in spec\u002Ftasks.yaml task by task, validating each against its acceptance criteria and halting at checkpoints. Use this skill whenever the user asks to implement, execute, run, continue, or work on a plan; when a spec\u002F directory with tasks.yaml exists in the repo; when they reference task or phase IDs (task-N.M, phase-N); or when they ask to start the next task or phase.","markpollack\u002Fagent-judge-tutorial","markpollack","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F247466?v=4","01M736J0CPEDMTXXKE50KECFAD","Mark Pollack","01M736J0DRJPW0DPFSK9A0JZVN",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmarkpollack\u002Fagent-judge-tutorial\u002Fblob\u002Fmain\u002Fcase-studies\u002Fspec-driven-petclinic\u002Ffixtures\u002Fpetclinic\u002Fappointment-scheduling-spec-with-usecases\u002F.claude\u002Fskills\u002F06-execute\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: execute\ndescription: Execute the implementation plan in spec\u002Ftasks.yaml task by task, validating each against its acceptance criteria and halting at checkpoints. Use this skill whenever the user asks to implement, execute, run, continue, or work on a plan; when a spec\u002F directory with tasks.yaml exists in the repo; when they reference task or phase IDs (task-N.M, phase-N); or when they ask to start the next task or phase.\n---\n\n# Execute Skill\n\nExecute the pre-approved implementation plan in `spec\u002Ftasks.yaml` task by task, validate each task, and halt at\ncheckpoints for approval.\n\nThis is the implementation phase of a spec-driven development workflow, after the plan has been generated and the review\nhas gated it as ready.\n\nPipeline position: proposal → spec → criteria → rules → review → plan → **execute**\n\n# Role\n\nYou execute tasks in order, validate them, and report progress. You do not modify anything under `\u002Fspec\u002F` except\n`status.md`. You do not skip tasks, reorder them, or proceed past checkpoints without explicit approval.\n\n# Inputs\n\n- Plan: @file:spec\u002Ftasks.yaml (task list)\n- Acceptance criteria: @file:spec\u002Fcriteria.md (validation source)\n- Technical constraints: @file:spec\u002Frules.md (constraint set)\n- Feature context: @file:spec\u002Fspec.md\n- Pipeline verdict and risk hotspots: @file:spec\u002Freview.md\n- Progress: @file:spec\u002Fstatus.md (you maintain this; create if missing)\n\n# Initialization\n\nWhen starting work:\n\n1. Read `tasks.yaml`. This is your task list.\n2. Read `criteria.md` and `rules.md`.\n3. Read `spec.md` for feature context and `review.md` for risk hotspots that map to specific tasks.\n4. Read `status.md` to find your position. If it doesn't exist, create it with `phase-1` \u002F `task-1.1` as `NOT_STARTED`.\n5. Set `current_task` to the first task with status `NOT_STARTED`.\n\n# Execution Loop\n\nFor each task:\n\n1. **Verify prerequisites.** For every `task_id` in `task.depends_on`, confirm its status is `COMPLETE` in `status.md`.\n   If not, halt with a Blocker report.\n\n2. **Mark in progress.** Update `status.md`: set the task to `IN_PROGRESS`.\n\n3. **Execute.** Read the task's `description`, `artifact`, `covers.acs`, and `covers.rules`. Produce or update the\n   artifact, plus any supporting files (tests, fixtures, configs) needed to satisfy validation. Apply every constraint\n   listed in `covers.rules`. Do not modify files unrelated to this task.\n\n4. **Validate.** Run the check described in `task.validation`. Then verify every AC in `covers.acs` is satisfied,\n   typically through passing tests or behavioral checks against `criteria.md`. If validation fails, take up to two\n   corrective attempts. Each attempt must be a different approach, not a re-run of the same code. If still failing after\n   two attempts, halt with a Blocker report.\n\n5. **Mark complete.** Update `status.md`: set the task to `COMPLETE`. Record any non-obvious decisions in the notes.\n\n6. **Advance.** If more tasks remain in the phase, set `current_task` to the next one. If this was the last task of the\n   phase, generate a Checkpoint report and halt for approval.\n\nWhen all phases complete, generate a Completion report.\n\n# Approval Responses\n\nAfter a Checkpoint report, wait for one of:\n\n- `APPROVED`: proceed to the next phase.\n- `APPROVED WITH NOTES: \u003Cnotes>`: record notes in `status.md`, then proceed.\n- `REVISE: task-N.M - \u003Cinstructions>`: apply the revision to the named task, re-validate, then resume.\n- `ROLLBACK: task-N.M`: mark the named task `NOT_STARTED`, undo its artifact, then resume from there.\n- `BLOCKED: \u003Creason>`: record blocker in `status.md` and halt.\n\nAfter a Blocker report, wait for one of:\n\n- `PROCEED WITH: \u003Coption number>`: continue using the specified option from the report.\n- `PROCEED WITH: \u003Ccustom instructions>`: continue using user-provided guidance.\n- `ABORT TASK`: skip this task and adjust the plan.\n\n# Status File Format\n\nMaintain `spec\u002Fstatus.md` with only the delta from `tasks.yaml`. Everything else is derivable.\n\n```markdown\n# Status: \u003Cfeature>\n\n## Current\n\n- Task: task-N.M\n- Status: IN_PROGRESS | NOT_STARTED | BLOCKED\n\n## Completed\n\n- task-1.1\n- task-1.2\n\n## Phase Approvals\n\n- phase-1: APPROVED\n- phase-2: PENDING\n\n## Blockers\n\n(empty if none)\n\n## Deviations\n\n(approved deviations from plan, with task ID and reason)\n\n## Notes\n\n(non-obvious decisions, per task)\n```\n\n# Checkpoint Report\n\n```markdown\n# Checkpoint: phase-N complete\n\n## Summary\n\n- Phase: phase-N, \u003Cname>\n- Tasks: \u003Cn>\u002F\u003Cn> complete\n\n## Artifacts\n\n| File   | Purpose    |\n|--------|------------|\n| \u003Cpath> | \u003Cone-line> |\n\n## AC Coverage (this phase)\n\n| AC   | Status    | Verified in    |\n|------|-----------|----------------|\n| AC-1 | satisfied | \u003Cfile or test> |\n\n## Validation\n\n- Compilation: PASS | FAIL\n- Tests: \u003Cn>\u002F\u003Cn> passing\n- Constraints (this phase's RULES): \u003Cn>\u002F\u003Cn> satisfied\n\n## Notes\n\n\u003Cambiguities resolved, deviations, concerns; empty if none>\n\nCHECKPOINT REACHED. AWAITING APPROVAL.\n```\n\n# Blocker Report\n\n```markdown\n# BLOCKED: task-N.M\n\n## Type\n\nSPEC_AMBIGUITY | SPEC_CONFLICT | TECHNICAL | VALIDATION_FAILURE | DEPENDENCY\n\n## Summary\n\n\u003Cone sentence>\n\n## Details\n\n\u003Cfull explanation>\n\n## Evidence\n\n\u003Ccode, error messages, spec quotes>\n\n## Attempted Solutions\n\n1. \u003Cwhat you tried> → \u003Cresult>\n2. \u003Cwhat you tried> → \u003Cresult>\n\n## Options\n\n1. \u003Coption>\n   - Impact: \u003Cplan, timeline, architecture>\n   - Tradeoff: \u003Cpros, cons>\n2. \u003Coption>\n   - Impact: \u003C...>\n   - Tradeoff: \u003C...>\n\n## Recommendation\n\n\u003Cwhich option and why>\n\nBLOCKED. AWAITING RESOLUTION.\n```\n\n# Completion Report\n\n```markdown\n# Feature Complete: \u003Cfeature>\n\n## Summary\n\n- Phases: \u003Cn>\u002F\u003Cn> complete\n- Tasks: \u003Cn>\u002F\u003Cn> complete\n- ACs satisfied: \u003Cn>\u002F\u003Cn>\n- RULES applied: \u003Cn>\u002F\u003Cn>\n\n## Coverage\n\n| AC   | Implemented in |\n|------|----------------|\n| AC-1 | \u003Cfile or test> |\n\n## Deviations from Plan\n\n\u003Cdeviations approved during execution; empty if none>\n\n## Open Items\n\n\u003Canything intentionally deferred, with reason>\n```\n\n# Rules\n\n- The `\u002Fspec\u002F` directory is read-only during implementation. The single exception is `status.md`, which you maintain.\n- Do not skip tasks or reorder within a phase.\n- Do not proceed past a checkpoint without an approval response.\n- Do not proceed when blocked without a resolution response.\n- A task may touch supporting files (tests, fixtures, configs) needed to satisfy `validation`, but must not modify files\n  unrelated to the task's `artifact` and coverage.\n- Record non-obvious decisions in the per-task notes in `status.md`.\n","# Execute Skill\n\nExecute the pre-approved implementation plan in `spec\u002Ftasks.yaml` task by task, validate each task, and halt at\ncheckpoints for approval.\n\nThis is the implementation phase of a spec-driven development workflow, after the plan has been generated and the review\nhas gated it as ready.\n\nPipeline position: proposal → spec → criteria → rules → review → plan → **execute**\n\n# Role\n\nYou execute tasks in order, validate them, and report progress. You do not modify anything under `\u002Fspec\u002F` except\n`status.md`. You do not skip tasks, reorder them, or proceed past checkpoints without explicit approval.\n\n# Inputs\n\n- Plan: @file:spec\u002Ftasks.yaml (task list)\n- Acceptance criteria: @file:spec\u002Fcriteria.md (validation source)\n- Technical constraints: @file:spec\u002Frules.md (constraint set)\n- Feature context: @file:spec\u002Fspec.md\n- Pipeline verdict and risk hotspots: @file:spec\u002Freview.md\n- Progress: @file:spec\u002Fstatus.md (you maintain this; create if missing)\n\n# Initialization\n\nWhen starting work:\n\n1. Read `tasks.yaml`. This is your task list.\n2. Read `criteria.md` and `rules.md`.\n3. Read `spec.md` for feature context and `review.md` for risk hotspots that map to specific tasks.\n4. Read `status.md` to find your position. If it doesn't exist, create it with `phase-1` \u002F `task-1.1` as `NOT_STARTED`.\n5. Set `current_task` to the first task with status `NOT_STARTED`.\n\n# Execution Loop\n\nFor each task:\n\n1. **Verify prerequisites.** For every `task_id` in `task.depends_on`, confirm its status is `COMPLETE` in `status.md`.\n   If not, halt with a Blocker report.\n\n2. **Mark in progress.** Update `status.md`: set the task to `IN_PROGRESS`.\n\n3. **Execute.** Read the task's `description`, `artifact`, `covers.acs`, and `covers.rules`. Produce or update the\n   artifact, plus any supporting files (tests, fixtures, configs) needed to satisfy validation. Apply every constraint\n   listed in `covers.rules`. Do not modify files unrelated to this task.\n\n4. **Validate.** Run the check described in `task.validation`. Then verify every AC in `covers.acs` is satisfied,\n   typically through passing tests or behavioral checks against `criteria.md`. If validation fails, take up to two\n   corrective attempts. Each attempt must be a different approach, not a re-run of the same code. If still failing after\n   two attempts, halt with a Blocker report.\n\n5. **Mark complete.** Update `status.md`: set the task to `COMPLETE`. Record any non-obvious decisions in the notes.\n\n6. **Advance.** If more tasks remain in the phase, set `current_task` to the next one. If this was the last task of the\n   phase, generate a Checkpoint report and halt for approval.\n\nWhen all phases complete, generate a Completion report.\n\n# Approval Responses\n\nAfter a Checkpoint report, wait for one of:\n\n- `APPROVED`: proceed to the next phase.\n- `APPROVED WITH NOTES: \u003Cnotes>`: record notes in `status.md`, then proceed.\n- `REVISE: task-N.M - \u003Cinstructions>`: apply the revision to the named task, re-validate, then resume.\n- `ROLLBACK: task-N.M`: mark the named task `NOT_STARTED`, undo its artifact, then resume from there.\n- `BLOCKED: \u003Creason>`: record blocker in `status.md` and halt.\n\nAfter a Blocker report, wait for one of:\n\n- `PROCEED WITH: \u003Coption number>`: continue using the specified option from the report.\n- `PROCEED WITH: \u003Ccustom instructions>`: continue using user-provided guidance.\n- `ABORT TASK`: skip this task and adjust the plan.\n\n# Status File Format\n\nMaintain `spec\u002Fstatus.md` with only the delta from `tasks.yaml`. Everything else is derivable.\n\n```markdown\n# Status: \u003Cfeature>\n\n## Current\n\n- Task: task-N.M\n- Status: IN_PROGRESS | NOT_STARTED | BLOCKED\n\n## Completed\n\n- task-1.1\n- task-1.2\n\n## Phase Approvals\n\n- phase-1: APPROVED\n- phase-2: PENDING\n\n## Blockers\n\n(empty if none)\n\n## Deviations\n\n(approved deviations from plan, with task ID and reason)\n\n## Notes\n\n(non-obvious decisions, per task)\n```\n\n# Checkpoint Report\n\n```markdown\n# Checkpoint: phase-N complete\n\n## Summary\n\n- Phase: phase-N, \u003Cname>\n- Tasks: \u003Cn>\u002F\u003Cn> complete\n\n## Artifacts\n\n| File   | Purpose    |\n|--------|------------|\n| \u003Cpath> | \u003Cone-line> |\n\n## AC Coverage (this phase)\n\n| AC   | Status    | Verified in    |\n|------|-----------|----------------|\n| AC-1 | satisfied | \u003Cfile or test> |\n\n## Validation\n\n- Compilation: PASS | FAIL\n- Tests: \u003Cn>\u002F\u003Cn> passing\n- Constraints (this phase's RULES): \u003Cn>\u002F\u003Cn> satisfied\n\n## Notes\n\n\u003Cambiguities resolved, deviations, concerns; empty if none>\n\nCHECKPOINT REACHED. AWAITING APPROVAL.\n```\n\n# Blocker Report\n\n```markdown\n# BLOCKED: task-N.M\n\n## Type\n\nSPEC_AMBIGUITY | SPEC_CONFLICT | TECHNICAL | VALIDATION_FAILURE | DEPENDENCY\n\n## Summary\n\n\u003Cone sentence>\n\n## Details\n\n\u003Cfull explanation>\n\n## Evidence\n\n\u003Ccode, error messages, spec quotes>\n\n## Attempted Solutions\n\n1. \u003Cwhat you tried> → \u003Cresult>\n2. \u003Cwhat you tried> → \u003Cresult>\n\n## Options\n\n1. \u003Coption>\n   - Impact: \u003Cplan, timeline, architecture>\n   - Tradeoff: \u003Cpros, cons>\n2. \u003Coption>\n   - Impact: \u003C...>\n   - Tradeoff: \u003C...>\n\n## Recommendation\n\n\u003Cwhich option and why>\n\nBLOCKED. AWAITING RESOLUTION.\n```\n\n# Completion Report\n\n```markdown\n# Feature Complete: \u003Cfeature>\n\n## Summary\n\n- Phases: \u003Cn>\u002F\u003Cn> complete\n- Tasks: \u003Cn>\u002F\u003Cn> complete\n- ACs satisfied: \u003Cn>\u002F\u003Cn>\n- RULES applied: \u003Cn>\u002F\u003Cn>\n\n## Coverage\n\n| AC   | Implemented in |\n|------|----------------|\n| AC-1 | \u003Cfile or test> |\n\n## Deviations from Plan\n\n\u003Cdeviations approved during execution; empty if none>\n\n## Open Items\n\n\u003Canything intentionally deferred, with reason>\n```\n\n# Rules\n\n- The `\u002Fspec\u002F` directory is read-only during implementation. The single exception is `status.md`, which you maintain.\n- Do not skip tasks or reorder within a phase.\n- Do not proceed past a checkpoint without an approval response.\n- Do not proceed when blocked without a resolution response.\n- A task may touch supporting files (tests, fixtures, configs) needed to satisfy `validation`, but must not modify files\n  unrelated to the task's `artifact` and coverage.\n- Record non-obvious decisions in the per-task notes in `status.md`.\n",{"name":5,"description":7},"main","2ad2b03c85e63e00324d18f7f57e61a3b0ad4b3f","case-studies\u002Fspec-driven-petclinic\u002Ffixtures\u002Fpetclinic\u002Fappointment-scheduling-spec-with-usecases\u002F.claude\u002Fskills\u002F06-execute","https:\u002F\u002Fgithub.com\u002Fmarkpollack\u002Fagent-judge-tutorial","https:\u002F\u002Fgithub.com\u002Fmarkpollack","2026-11-12 05:27:23",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add markpollack\u002Fagent-judge-tutorial --skill execute",{"tool":36,"command":37},"bunx","bunx skills add markpollack\u002Fagent-judge-tutorial --skill execute",{"tool":39,"command":40},"pnpm","pnpm dlx skills add markpollack\u002Fagent-judge-tutorial --skill execute","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmarkpollack\u002Fagent-judge-tutorial\u002Fblob\u002Fmain\u002Fcase-studies\u002Fspec-driven-petclinic\u002Ffixtures\u002Fpetclinic\u002Fappointment-scheduling-spec-with-usecases\u002F.claude\u002Fskills\u002F06-execute\u002FSKILL.md",true,[44],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},".intellij-skill-source","OTHER","其他",24,"https:\u002F\u002Fgithub.com\u002Fmarkpollack\u002Fagent-judge-tutorial\u002Fblob\u002Fmain\u002Fcase-studies\u002Fspec-driven-petclinic\u002Ffixtures\u002Fpetclinic\u002Fappointment-scheduling-spec-with-usecases\u002F.claude\u002Fskills\u002F06-execute\u002F.intellij-skill-source",[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M736KCZ1PZH2KW52XZRBXZSA","grilling","Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.","https:\u002F\u002Fgithub.com\u002Fmarkpollack\u002Fagent-judge-tutorial\u002Fblob\u002Fmain\u002Fcase-studies\u002Fspec-driven-petclinic\u002Ffixtures\u002Fpetclinic\u002Fappointment-scheduling-spec-with-usecases\u002F.claude\u002Fskills\u002Fgrilling\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M736KAW9ESTST1K61YZBFYSQ","grill-me","A relentless interview to sharpen a plan or design.","https:\u002F\u002Fgithub.com\u002Fmarkpollack\u002Fagent-judge-tutorial\u002Fblob\u002Fmain\u002Fcase-studies\u002Fspec-driven-petclinic\u002Ffixtures\u002Fpetclinic\u002Fappointment-scheduling-spec-with-usecases\u002F.claude\u002Fskills\u002Fgrill-me\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"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},"01M736K3NX5CHWB756HFM8JJEB","tasks","Generate an implementation task list from validated spec artifacts","https:\u002F\u002Fgithub.com\u002Fmarkpollack\u002Fagent-judge-tutorial\u002Fblob\u002Fmain\u002Fcase-studies\u002Fspec-driven-petclinic\u002Ffixtures\u002Fpetclinic\u002Fappointment-scheduling-spec-with-usecases\u002F.claude\u002Fskills\u002F05-tasks\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":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M736K1RM2B2PEDHAYG8EB09E","spec-review","Stress-test the spec pipeline outputs against each other and the codebase before implementation begins","https:\u002F\u002Fgithub.com\u002Fmarkpollack\u002Fagent-judge-tutorial\u002Fblob\u002Fmain\u002Fcase-studies\u002Fspec-driven-petclinic\u002Ffixtures\u002Fpetclinic\u002Fappointment-scheduling-spec-with-usecases\u002F.claude\u002Fskills\u002F04-review\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M736JZ3K7TDMVVQ47KDAAEF0","rules","Capture feature-level design decisions and the technical constraints that follow, traceable to acceptance criteria","https:\u002F\u002Fgithub.com\u002Fmarkpollack\u002Fagent-judge-tutorial\u002Fblob\u002Fmain\u002Fcase-studies\u002Fspec-driven-petclinic\u002Ffixtures\u002Fpetclinic\u002Fappointment-scheduling-spec-with-usecases\u002F.claude\u002Fskills\u002F03-rules\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M736JX45ESXX1N7863G9X3JC","criteria","Translate the spec into a complete, traceable set of acceptance criteria in EARS form","https:\u002F\u002Fgithub.com\u002Fmarkpollack\u002Fagent-judge-tutorial\u002Fblob\u002Fmain\u002Fcase-studies\u002Fspec-driven-petclinic\u002Ffixtures\u002Fpetclinic\u002Fappointment-scheduling-spec-with-usecases\u002F.claude\u002Fskills\u002F02-criteria\u002FSKILL.md",[],[]]