Skills
A skill is a reusable procedure your AI tool follows when you ask — an impact analysis, a change record, a prompt rebuild.
- SkillUSD 2
Work Breakdown
Keeps your task list honest: every task mapped to a milestone, statuses dated, finished work recorded, and new work slotted where it belongs — the difference between a plan and a wish list.
Best for: Plans that stopped matching reality weeks ago
- SkillUSD 2
Milestone Tracker
Maintains the milestone list itself: plain-language definitions of done, honest statuses with dates, and the discipline that a milestone is achieved when its criteria are met — not when it feels finished.
Best for: Reporting progress to stakeholders without hand-waving
- SkillUSD 2
Change Specification
Writes the one-page specification a change needs before anyone builds it: exactly what is impacted, what each task covers, what done means, and a resume-here section so work survives interruptions.
Best for: Changes big enough to lose track of mid-way
- SkillUSD 2
Impact Register
Records an impact analysis where it can govern the work: the inventory of touched elements written into the change's specification, kept current as scope moves, so nothing found is later forgotten.
Best for: Turning impact findings into a tracked checklist
- SkillUSD 2
Capability Gap Check
Checks whether your team of agents and skills can actually deliver the steps a goal needs, names the gaps, and keeps a register of missing capabilities so they get built deliberately instead of discovered painfully.
Best for: Before committing to a goal with an AI team
- SkillUSD 2
Stack Check
Checks any proposed library, service or tool against the stack you have approved — what already covers the need, what the addition truly costs, and a written case when adding something is genuinely right.
Best for: Stopping dependency sprawl before it starts
- SkillUSD 2
Decision Record
Writes a decision down the moment it is made — what was decided, by whom, why, and exactly which earlier statements it supersedes — so direction changes become documents instead of folklore.
Best for: Decisions that change product rules or architecture
- SkillUSD 2
Release Audit
A read-only GO/NO-GO check before you deploy: tests, build, configuration, target health and pending migrations — everything inspected, nothing changed, verdict in writing.
Best for: The five minutes before any production deploy
- SkillUSD 2
First Release
Walks a project through its very first deployment to a fresh server or environment: prerequisites verified, the full release laid down step by recorded step, and the result proven live before anyone celebrates.
Best for: The nerve-racking first production deploy
- SkillUSD 2
Update Release
Ships a normal update to an already-running system: gates first, the delta deployed by your procedure, data migrations handled with care, the previous release kept warm for rollback, and the result verified.
Best for: The routine deploys that should stay routine
Also see the Agents.