Agent Skills
› NeverSight/learn-skills.dev
› validate-change-plan
validate-change-plan
GitHub在实施前验证故事或缺陷的变更计划，确保其符合范围、具备完整任务与验证步骤。通过则标记为Ready，未通过则标记为Blocked并说明原因，对齐制品状态。
Trigger Scenarios
用户请求验证变更计划
add-story或add-bugfix操作后需确认状态
检查待验证的故事或缺陷列表
Install
npx skills add NeverSight/learn-skills.dev --skill validate-change-plan -g -y
SKILL.md
Frontmatter
{
"name": "validate-change-plan",
"description": "Validate one epic-scoped or standalone story or bugfix change plan before implementation. Use after `add-story` or `add-bugfix` to confirm or correct the selected artifact's `Ready` or `Blocked` state."
}
Validate Change Plan
Core Rule
Validate the written story or bugfix plan, not memory. Confirm exactly one change plan is ready to feed implement-change: it fits its selected placement, has complete implementation tasks, concrete verification, and no blocking open questions. Keep the selected artifact state aligned with the result: passing plans are Ready; non-passing plans are Blocked with Blocked By filled. Follow references/clarification-policy.md.
Workflow
-
Load validation context:
- When the user has not provided a specific artifact path, run this skill's
scripts/list-unvalidated-plans.sh <target-repo-root>to findReadyorBlockedstories and bugfixes whoseChange Plan Validationdecision is missing or notPass; use that filtered list to choose or ask for the single plan to validate. - Read one epic-scoped story or bugfix under
docs/epics/active/<epic>/story_*.mdordocs/epics/active/<epic>/bugfix_*.md, or one standalone story or bugfix underdocs/standalone-changes/active/story_*.mdordocs/standalone-changes/active/bugfix_*.md. - For epic-scoped work, read
docs/epics/active/<epic>/epic.mdand its source Product Vision when present. - For standalone work, read
docs/vision.mdwhen present, active epics underdocs/epics/active/, and sibling standalone changes underdocs/standalone-changes/active/. - Read relevant concern specs, sibling stories, sibling bugfixes, and code evidence when they affect scope, placement, or verification.
- When the user has not provided a specific artifact path, run this skill's
-
Validate placement fit:
- For epic-scoped work, check that the selected story or bugfix stays inside epic scope and does not contradict the Product Vision, epic, concern specs, or sibling stories or bugfixes.
- For standalone work, check that the routing decision explains why no active epic fits, why no new epic is needed, and how the work stays consistent with Product Vision, concern specs, and sibling standalone changes.
- Check that any scope change, public behavior change, rollout change, material risk, or durable product direction change is reflected in the owning artifact; otherwise mark the item
BlockedorFailand recommendadd-story,add-bugfix,create-epic, ordefine-product-visionas appropriate.
-
Validate change plan readiness:
- For stories, check acceptance criteria, regression boundaries, implementation tasks, verification matrix, assumptions, and open questions.
- For bugfixes, check current behavior, expected behavior, unchanged behavior, reproduction evidence, root cause, fix boundary, regression risks, implementation tasks, and verification matrix.
- Check that every implementation task has purpose, scope, dependencies, verification steps, and pass criteria.
- Check that verification methods are concrete enough to execute during
validate-implementation.
-
Update validation status:
- Update the selected story or bugfix's
Change Plan Validationsection with evidence, gaps, skipped checks, and a decision:Pass,Fail,Partial, orBlocked. - Set
State: Readywhen the decision isPass. - Set
State: Blockedand fillBlocked Bywith the concrete plan gap, dependency, question, or validation blocker when the decision isFail,Partial, orBlocked. - Set
Blocked By: N/Awhen the artifact isReady. - Add remediation implementation tasks or notes when coverage or verification is missing.
- Do not implement code; implementation belongs to
implement-change.
- Update the selected story or bugfix's
-
Report result:
- Summarize validation outcome, placement fit, coverage gaps, verification gaps, and blocking open questions.
- Recommend
implement-changewhen the result isPass; otherwise recommend the specific artifact skill needed to fix the gap.
Validation Checklist
- Selected story or bugfix fits its active epic, or standalone routing is justified and evidence-backed.
- Selected story or bugfix does not contradict sibling stories or bugfixes.
- Every acceptance, expected behavior, or unchanged behavior criterion has verification coverage.
- Every implementation task has concrete verification and pass criteria.
- Blocking open questions are resolved or recorded as
Blocked. - Result includes an overall decision:
Pass,Fail,Partial, orBlocked. - State is aligned to
Ready, orBlockedwith a concreteBlocked Byvalue. - Passing change plan can feed
implement-change.
Version History
- e0220ca Current 2026-07-05 23:30
