Skip to content

deanpeters/Product-Manager-Skills / skills/intel-discipline-advisor

intel-discipline-advisor

Verified

Triage a competitive or market question into the right intelligence disciplines, cadence, and executing skill. Use when you know something needs researching but not which channel to run.

FileKindSize
SKILL.mdskill md12.5 KB
examples/conversation-flow-industrial.mdmarkdown4.9 KB
examples/conversation-flow.mdmarkdown4.9 KB
template.mdmarkdown2.0 KB

template.md

View on GitHub
# Intel Triage Card Template

Copy this to record the outcome of an intel-discipline-advisor session — the triage decision as a
handoff artifact. It's deliberately small: the advisor's whole teaching is that two or three
disciplines matched to the decision beat coverage theater, and the card should fit on one screen
so it actually gets followed.

## Template

```markdown
# Intel Triage: [the question, in your words]

**Date:** [YYYY-MM-DD]
**Decision this feeds:** [what changes based on what we find]
**Situation type:** [suspected move / artifact build-or-refresh / structure puzzle / standing watch]
**Signal already seen:** [what tipped you off — this is 1 discipline already flagged, or "none"]
**Constraints:** [free sources only? geography? recurring time available?]

## The Route
| # | Discipline mix | Cadence | Executing skill | Artifact fed | Why this mix |
|---|---|---|---|---|---|
| 1 | | | | | |
| 2 | | | | | |

**Chosen:** [which recommendation(s), and who runs it]
**First action, this week:** [the single concrete next step]

## Corroboration ladder (for suspected moves)
- Already flagged: [discipline + signal]
- Would corroborate independently: [channels that fail differently from the seen signal]
- Escalation: 1 = watch item · 2 = working hypothesis · 3+ = brief leadership

## The off-ramp check
- [ ] Confirmed this is actually an intel question — not one that win/loss interviews,
      discovery, or your own support tickets answer better. If it is, route there and stop.

## Review date
[When to check whether the route produced anything — a cadence nobody revisits is false confidence]
```

## Quality checks before you call it done

- The route has 2-3 rows, not 8 — a full-table route means the triage didn't happen
- Each row's "why this mix" shows the artifact-mapping logic (the lesson travels with the card)
- The corroborating channels are *independent* of the seen signal — re-detecting the same signal type doesn't stack
- The cadence matches the honest time answer, not the aspirational one
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 323kUpdated Claude CodeCodexVerifiedInstall