Skip to content
Back to skills

Aid Discovery

BSecurity

AID Phase 0 - Research & discovery. Use for validating problem spaces, identifying stakeholders, defining success metrics, deciding whether to proceed.

  • 9 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 9, 2026
devopsgo

Security analysis

B88/100
  • criticalImpersonates system messages to override safety constraints

Pro scans all 4 files and shows the line behind each finding

Scanned September 9, 2026

npx -y skills add ilandahan/AID --skill aid-discovery --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Aid Discovery?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Aid Discovery
[![Security: B — Skills Directory](https://www.skillsdirectory.com/api/skills/ilandahan-aid-discovery/badge)](https://www.skillsdirectory.com/skills/ilandahan-aid-discovery)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: aid-discovery
description: AID Phase 0 - Research & discovery. Use for validating problem spaces, identifying stakeholders, defining success metrics, deciding whether to proceed.
---

# aid-discovery - AID Phase 0

Purpose: Validate problem space before committing to solution.
Entry: Initial idea/request exists, stakeholders available.
Exit: Problem validated, stakeholders identified, success metrics defined, go/no-go decision.

## Deliverables

1. Problem Statement (SCQ format) - Validated, no solution assumptions
2. Stakeholder Map - All affected parties identified
3. Success Metrics - Quantified, measurable outcomes

## Discovery Questions

Ask these:

- Problem: What problem are we solving? Who has this problem? How painful? (Quantify) What if we don't solve it?
- Stakeholders: Who are end users? Who owns data/process? Who makes decisions? Who else touches this?
- Success: What does success look like? How will we measure? What's minimum viable outcome?
- Technical feasibility: Is this feasible? Major technical risks? Required skills? Infrastructure needs?

## Problem Statement Template (SCQ)

```markdown
## Problem Statement

### Situation
[Current state]

### Complication
[What's wrong]

### Question
[What solving this answers]

### Impact
- [Quantified impact]

### Success Metrics
| Metric | Current | Target |
|--------|---------|--------|
| [Metric] | [Now] | [Goal] |
```

## Stakeholder Map Template

```markdown
### Decision Makers
- [Name/Role]: [Responsibility]

### Data/System Owners
- [Name/Role]: [What they own]

### End Users
- [Type]: [How affected]

### Integrations
- [System]: [Relationship]
```

## Common Pitfalls

|Pitfall|Fix|
|---|---|
|Solution-first|Start with "what problem?"|
|Missing stakeholders|Ask "who else touches this?"|
|Vague problems|If can't measure, not defined|
|Assumption blindness|Make assumptions explicit|

## Phase Gate Checklist

- [ ] Problem statement validated
- [ ] All stakeholders identified
- [ ] Success metrics specific
- [ ] Technical feasibility assessed
- [ ] Proceed/not-proceed decision clear
- [ ] Scope boundaries established

## Handoff to PRD

- Validated problem statement
- Stakeholder map
- Success metrics
- Constraints identified
- Scope boundaries

Files in this skill

  • SKILL.extended.md6.1 KB
  • SKILL.md2.2 KB
  • references/discovery-workshop-guide.md2.5 KB
  • references/feasibility-assessment.md3.4 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.