gadflylisted
Install: claude install-skill sgtlaugh/skills
# /gadfly - sting the design awake
Socrates called himself Athens' gadfly: the fly that stings a complacent horse into motion. This skill questions a **tech spec / architecture doc** until its weak points show, before the team builds the wrong thing.
Spec review has no mechanical oracle, and a wrong architectural criticism sends a team chasing a flaw that isn't there. So every finding is a **hypothesis with a confidence and a check that settles it**, never a verdict.
Flow: **Phase 0** ingest → **Phase 1** requirements gate → **Phase 2** ground in the code → **Phase 3** attack → report. `--prd` adds a WHY-vs-HOW coverage check.
## Usage
```
/gadfly <confluence-url> # fetch + interrogate a Confluence spec
/gadfly <page-id> # bare Confluence page id
/gadfly <file-path> # local spec: .md / .txt / .pdf / .docx
/gadfly <spec> --prd <prd> # also cross-check against a PRD (WHY-vs-HOW); prd = path or url
```
A drafted solution is a spec too: run `/gadfly` on your own design (a new schema, a permission model), refine, repeat.
## Phase 0 - Ingest the spec
Resolve the input to **spec text + a version stamp**, and record what you could NOT read. Never silently skip content.
### Confluence (URL or bare page id)
Shell state does not persist between tool calls - prepend these lines to EVERY bash call that hits Confluence (the page fetch AND each diagram download):
```bash
C=${CLAUDE_SKILLS_CREDENTIALS:-$HOME/.config/claude-skills/credentials.json}
JIRA