assumption-tracker
Explicitly track, test, and validate assumptions - prevent blind spots
npx skills add majiayu000/claude-skill-registry --skill assumption-tracker --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Skill: assumption-tracker ## What I do I surface and manage hidden assumptions. I ensure that every leap of faith in a design or plan is documented, tiered by risk, and systematically validated through evidence or testing. ## When to use me - Before starting a new feature or architectural change - When requirements are ambiguous or "common sense" is invoked - During technical planning sessions to identify "we think" vs "we know" - When evaluating third-party libraries or external API behaviours ## Core principles 1. **Surface the hidden** — If it isn't proven, it's an assumption. 2. **Tier by risk** — Focus validation on assumptions with high impact and low certainty. 3. **Validate early** — Use spikes, prototypes, or data lookups to turn assumptions into facts. 4. **Document outcomes** — Record whether an assumption was proven true or false. ## Patterns & examples **Assumption Logging Format:** | Assumption | Impact (H/M/L) | Certainty (H/M/L) | Validation Method | Status | | :--- | :--- | :--- | :--- | :--- | | "The legacy API supports concurrent writes." | High | Low | Run concurrency spike test | Pending | | "Users prefer the sidebar over the top nav." | Medium | Medium | Rev
- What I do
- When to use me
- Core principles
- Patterns & examples
- Anti-patterns to avoid
- KB Reference
- Related skills
What does the assumption-tracker skill do?
Explicitly track, test, and validate assumptions - prevent blind spots
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill assumption-tracker --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
