From techlead
Verifies task alignment with docs/GOAL.md, docs/ROADMAP.md, and docs/SPEC.md before any code change. Use this skill automatically before writing or editing code, when the user asks to implement a feature, fix a bug, refactor code, or do any coding work. Also trigger when the user asks "should I work on X?" or discusses priorities. If the project has docs/GOAL.md or docs/ROADMAP.md, this check must happen before code touches disk. Also checks docs/SPEC.md conformance if it exists.
How this skill is triggered — by the user, by Claude, or both
Slash command
/techlead:check-alignmentThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Verify that the current task aligns with the project's goal and active roadmap before writing code.
Verify that the current task aligns with the project's goal and active roadmap before writing code.
Before any code is written or modified. This is a gate — code does not get written until alignment is confirmed.
Read docs/GOAL.md and docs/ROADMAP.md. For specs, use docs/specs/README.md if it exists, else docs/SPEC.md.
docs/GOAL.md is missing: stop and say "No docs/GOAL.md found. Run /init-techlead to set up
your project documents first."docs/ROADMAP.md is missing: stop and say "No docs/ROADMAP.md found. Run /init-techlead to
set up your project documents first."docs/specs/README.md nor docs/SPEC.md exists: that's fine — it's optional. Proceed without it.Ask yourself two questions:
If docs/SPEC.md exists and the task relates to a specified capability:
This change would diverge from docs/SPEC.md: [capability] specifies "[behavior]". Should we update the spec first, or adjust the implementation?
Both true → proceed silently. Don't announce that alignment passed — just do the work.
Goal-aligned but wrong milestone → stop and ask:
This task is in the [Next/Later] section of docs/ROADMAP.md, not Now. Want to reprioritize it to Now before I proceed?
Not goal-aligned → stop and ask:
I can't connect this to the project goal: [goal text]. Can you explain how it fits, or should we update docs/GOAL.md?
When alignment passes, don't waste the user's time announcing it. Just proceed with the task. The value of this check is in catching misalignment, not in reporting success.
npx claudepluginhub rroundtable/techlead --plugin techleadVerifies alignment between requirements/specs/PRDs and plans/tasks/implementation steps; detects coverage gaps, scope creep, design mismatches; rewrites tasks in TDD red/green/refactor format.
Reviews and updates a project roadmap by cross-referencing PRDs, stories, and code to identify done, blocked, or stale items; supports marking items complete, reprioritizing, and validating consistency.
Provides patterns for aligning features with PROJECT.md goals, validating scope boundaries, and checking architectural constraints before implementation.