impact
Use when asked to check the impact of an issue or its slice. Trace the consequences of changing a concept, contract, invariant, behavior, or artifact before implementation.
- License 许可
- MIT
- 最近更新
- 2026-10-14
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- impact
- description
- Use when asked to check the impact of an issue or its slice. Trace the consequences of changing a concept, contract, invariant, behavior, or artifact before implementation.
03 SKILL.md 正文
Mechanism: not yet
Find what actually depends on the subject being shaped, behaving, or meaning what it currently does.
Do not just search mentions. Follow semantic dependencies until the picture converges.
Check:
- durable docs and decisions
- product/API behavior
- code and composition
- tests, fixtures, parity/reference readers
- active tickets, open questions, RFCs
- upcoming work likely to depend on it
- historical context and records; history is maintained mechanically like everything else (
/mechanism, Mechanical by construction), not exempted from repair
Distinguish:
- must change
- must verify
- may simplify
- hidden risk
- historical only
- probably unaffected
Look especially for assumptions shared across docs, code, and tests: internal agreement does not prove external correctness.
Challenge the proposed change too:
- is it solving a demonstrated problem?
- can it be narrower?
- does it introduce a general abstraction?
- if so, what second materially different concrete shape justifies it?
The assessment is these four sections and nothing else. That governs its shape, never the turn: called from another skill, hand them back and carry on with the step that called.
Impact
Main blast radius.
Hidden edges
Non-obvious dependencies or risks.
Leave alone
Related things that should not change.
Recommendation
Proceed, narrow, rethink, or postpone, and why.
04 同仓库更多 Skills
verify
Use after an implementation pass, or to verify a landed slice before close. Whole verification of landed work: ticket, RFC, governing docs, and the project's verification set. Repair-and-report where that policy holds.
ticket
Use to decompose a parent work into independently-workable child tickets. Use to mint ticket(s), possibly a single one, when planning implementation without one.
tdd
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
spec
Use to develop a spec for substantial work through /align, then hand off to /ticket. Use when a change needs agreed scope, behavior, boundaries and testing before decomposition. An existing spec for the work is developed in place.
skill-up
Aid agent skill creation or modification. Use when creating a new skill or changing an existing one. Use whenever writing any agent instructions, whether to a file or directly in a reply.
setup-devops
Set up the project's engineering scaffolding, from toolchain to CICD and observability. Use when initializing a repo or filling a setup gap.