Spec aligning
Verifies implementation aligns with stated requirements and acceptance criteria. Use before implementation (to clarify scope) and before final sign-off (to detect gaps).From its SKILL.md
npx -y skills add haowjy/orchestrate --skill spec-aligningAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 19 stars19 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.4 KB, as published. Nobody here has run it
Spec Alignment
Use this skill to sanity-check whether work matches intent.
When Invoked
Good fit when:
- requirements are spread across multiple messages/files;
- a large change needs a quick "did we build the right thing?" pass;
- review or test signals conflict on expected behavior.
Inputs
Use whichever requirement sources are available, typically:
- explicit user instructions;
- plan/spec docs (plans, ADRs, acceptance notes);
- tests that encode intended behavior;
- recent implementation/review reports.
If sources conflict, call that out and proceed with the most defensible interpretation.
Suggested Approach
Suggested flow (adapt as needed):
- Extract the key requirements that matter for the decision at hand.
- Compare those requirements against available evidence (code/tests/reports).
- Identify confirmed alignment, likely gaps, and unresolved unknowns.
- Propose the smallest next step to reduce uncertainty or close a gap.
Output
Keep output concise and decision-oriented. A short structure that often works:
- what appears aligned;
- what looks misaligned or risky;
- what is still unknown;
- what to do next.
Use explicit evidence when possible, but keep the format flexible for the task.