brainstorming

Category: Content & Multimedia | Uploader: yimwoo | Downloads: 0 | Version: v1.0（Latest）

Use before any feature work — explores intent, requirements, and design. Produces HOTL contracts (intent, verification, governance) before implementation.

Changelog: Source: GitHub https://github.com/yimwoo/hotl-plugin

Directory Structure

Current level: skills/brainstorming/

📄 SKILL.md 1.9 KB

SKILL.md

---
name: brainstorming
description: "Use before any feature work — explores intent, requirements, and design. Produces HOTL contracts (intent, verification, governance) before implementation."
---

# HOTL Brainstorming

## Overview

Turn ideas into designs with explicit HOTL contracts. Ask questions one at a time. Present design for approval before any implementation.

<HARD-GATE>
Do NOT write any code or create any files until design is approved and hotl-workflow.md is generated by writing-plans.
</HARD-GATE>

## Process

1. **Explore context**
   - If user's message references a doc path → read it
   - Scan `docs/plans/` for existing design docs → if found, read the most recent 1-2 and summarize prior decisions
   - If neither exists, proceed normally
   - Also read relevant files, recent commits, existing patterns
2. **Ask clarifying questions** — one at a time, understand purpose/constraints/success criteria
3. **Propose 2-3 approaches** — with trade-offs and recommendation
4. **Present design in sections** — get approval after each section
5. **Define HOTL contracts** — always include all three:

### Intent Contract
```
intent: [one sentence goal]
constraints: [what must not change/break]
success_criteria: [how we know it's done]
risk_level: low | medium | high
```

### Verification Contract
```
verify_steps:
  - run tests: [test command]
  - check: [what to inspect]
  - confirm: [success signal]
```

### Governance Contract
```
approval_gates: [list of steps requiring human review]
rollback: [how to undo if something goes wrong]
ownership: [who is accountable]
```

6. **Write design doc** — save to `docs/plans/YYYY-MM-DD-<topic>-design.md`
7. **Invoke writing-plans** — transition to implementation planning

## Key Principles

- One question at a time
- YAGNI ruthlessly — remove unnecessary features
- Always propose alternatives before settling
- `risk_level: high` = security, auth, privacy, billing (always human-gated)

Comments 0

Latest | Hot

Please login before commenting.

No comments yet. Be the first one!

brainstorming

Directory Structure

SKILL.md

Report

Notice