Skip to main content
ClaudeWave
Skill50 estrellas del repoactualizado 1mo ago

[agent-name]

[One sentence — what this agent does and when it's triggered. Be specific enough that Claude can decide whether to invoke it.]

Instalar en Claude Code
Copiar
git clone --depth 1 https://github.com/radekamirko/C.R.I.S.P /tmp/-agent-name- && cp -r /tmp/-agent-name-/templates/agent- ~/.claude/skills/-agent-name-
Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

agent-skill.md

# [Agent Name]

## Responsibility

_(One paragraph. What is this agent's job? What problem does it solve within the system? What does it own end-to-end?)_

---

## Inputs

| # | Input | Type | Source | Required? | Notes |
|---|---|---|---|---|---|
| 1 | | string / number / object / array / file | user / API / DB / agent / context | Yes / No | |
| 2 | | | | | |

---

## Outputs

| # | Output | Type | Destination | Notes |
|---|---|---|---|---|
| 1 | | string / number / object / array | user / API / DB / agent | |
| 2 | | | | |

---

## Boundaries

> These are non-negotiable. Claude must follow them every time this agent runs.

**This agent must never:**
- 
- 

**This agent must always:**
- 
- 

**Human-in-the-loop triggers:**
_(List any output or situation that requires human review before the agent proceeds or commits)_
- 

**Fallback behavior:**
_(What does this agent do if inputs are incomplete, an API fails, or confidence is low?)_
- 

---

## Handoffs

### Calls (outbound)

| Agent / Service | When | Input passed | Output expected |
|---|---|---|---|
| | _(condition that triggers the call)_ | | |

### Called by (inbound)

| Agent / Trigger | When this agent is invoked | What it receives | What it returns |
|---|---|---|---|
| | | | |

_(None — if this agent is standalone)_

---

## System Prompt

> This is the prompt injected as system context when this agent runs.
> Edit this carefully — tone, constraints, and framing live here.

```
You are [agent name], a [role description] for [product name].

Your job: [one sentence description of the core task]

## Context you will receive
[Describe what structured context is passed in — user profile, data snapshot, etc.]

## Your output
[Describe exactly what you return — format, structure, tone]

## Rules
- [Non-negotiable constraint]
- [Non-negotiable constraint]
- [Non-negotiable constraint]

## What you must never do
- [Hard boundary]
- [Hard boundary]

## Tone and language
- [Tone guideline]
- [Language constraint — e.g. "never use medical language"]
```

---

## Prompt Design Notes

_(Reasoning behind key prompt decisions — useful when revisiting or debugging output quality)_

- 
- 

---

## Quality Gates

Before this agent's output is used or shown to the user:

- [ ] Output is within expected format/structure
- [ ] No prohibited language used (check Boundaries above)
- [ ] Fallback triggered if confidence is low or inputs were incomplete
- [ ] Human-in-the-loop check passed if required

---

## Test Cases

| # | Scenario | Input | Expected output | Pass/Fail |
|---|---|---|---|---|
| T1 | Happy path — full inputs | | | |
| T2 | Partial inputs / missing data | | Fallback triggered, partial output flagged | |
| T3 | Boundary violation check | | Prohibited content absent from output | |

---

## Notes for Claude Code

_(Implementation specifics — where this agent lives in the codebase, how it's invoked, any library or API dependencies)_

- **File location:** `lib/agents/[name].ts` _(or equivalent)_
- **Invoked by:** _(screen / other agent / cron / background job)_
- **Dependencies:** _(APIs, DB tables, other agents)_
crisp-executeSkill

CRISP Execute — Sprint execution loop with change request management, security gates, product gates, and stakeholder reporting. Use after Phase S (Spec) is complete and crisp-state.json shows ready_for_execute: true. Triggers on "start sprint", "begin build", "execute", "sprint 1", "run sprints", or when handed off from crisp-orchestrator.

crisp-orchestratorSkill

CRISP session manager — detects project state and routes to the right entry point. Use /crisp to start or resume any CRISP engagement. Handles new projects (discovery), existing codebases (archaeology), active sprints (execute), and validation (prove). Reads docs/crisp-state.json to know where you are.

crisp-reportSkill

Generate a beautiful single-file HTML report from the project's docs/ folder. Works after any CRISP phase, after Archaeology, or at sprint close in Execute. Triggers on "generate report", "export docs", "create HTML report", "share docs", or automatically at sprint close in CRISP Execute.

crisp-startSkill

Begin a CRISP product discovery session — Phase C (Clarify)

phase1-clarifySkill

The Mileva Method (CRISP) — Phase 1: Clarify. Problem definition, eliciting, painkiller test, buy vs build, AI justification gate, Go/No-Go. Use at the start of any AI implementation project. Triggers on "clarify", "phase 1", "start discovery", "define the problem", "what problem are we solving", or at the beginning of a new client engagement.

phase2-resultsSkill

The Mileva Method (CRISP) — Phase 2: Results. Outcome alignment, stakeholder register, baseline measurement, success metrics, tradeoff negotiation. Use after problem definition is complete. Triggers on "results", "phase 2", "define success", "success metrics", "what does done look like", or after Phase C exit checklist is complete.

phase3-investigateSkill

The Mileva Method (CRISP) — Phase 3: Investigate. Process mapping for existing or greenfield processes, user journey mapping, UX discovery, project goals, system architecture (integration map + data flow). Use after outcome alignment. Triggers on "investigate", "phase 3", "map the process", "process mapping", "user journey", "as-is process", or after Phase R exit checklist is complete.

phase4-specSkill

The Mileva Method (CRISP) — Phase 4: Spec. Full implementation readiness package including solution design, UX direction, tech stack, backlog, MVP prioritization, risk assessment, and AI architecture for Claude Code projects — CLAUDE.md, skill mapping, AI specs, sprint planning, quality gates. Triggers on "spec", "phase 4", "build ready", "implementation plan", "CLAUDE.md", "sprint planning", "backlog", "AI spec", or after Phase I exit checklist is complete.