speciallisted

# special The audit skills walk the line looking for what is broken. `special` walks the walk-in looking for what is possible. The chef sees what is fresh and plentiful on the shelves and proposes the dish worth adding to the board tonight, the one that uses what is already in the kitchen. A special is not invented out of nothing; it is the obvious next thing made from what you already have. **Core principle:** every proposal is grounded in evidence already in the repo. **If you cannot point to the signal in the walk-in, it is not a special, it is a daydream.** No trend-chasing, no wishlist, no feature you cannot tie to something that already exists. **Read-only.** `special` proposes; it never builds. Picking the dish and cooking it are later steps. ## What this is not - Not the audit trio. [line-check](../line-check/SKILL.md), [bug-hunt](../bug-hunt/SKILL.md), and [security-sweep](../security-sweep/SKILL.md) find problems. `special` finds opportunities. A bug is not a feature. - Not [mise](../mise/SKILL.md). mise designs an idea you already have. `special` finds the idea worth designing. A chosen special flows into mise next. ## Read the kitchen first Before proposing anything, read what the project says it is and is not: README, CLAUDE.md / AGENTS.md, docs, declared roadmap, stated non-goals. A proposal that contradicts a declared non-goal is cut, or flagged as a deliberate challenge to it with that called out. Know the dish before you suggest the next course. ## Th