A requirements and implementation planning tool. It turns an idea or feature request into a structured `DESIGN.md` document with scope, requirements, and constraints.

Use it to document a new project or feature, identify missing requirements, and define acceptance criteria.

It helps clarify what should be built before technical design and coding begin. This reduces ambiguity about expected behavior and limits.

dare-design — Skill by dewtech-technologies

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add skills/dewtech-technologies/dare-method/dare-design

Any agent

npx skills add dewtech-technologies/dare-method --skill dare-design

Clone the repo

git clone --depth 1 https://github.com/dewtech-technologies/dare-method

Made for: Claude Code, Codex.

Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,417 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00048	$0.01417
Opus 5	$0.00024	$0.00709
Sonnet 5	$0.00010	$0.00283
Haiku 4.5	$0.00005	$0.00142

Measured 3d ago against content hash f52c9ef6ad39, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

dare-design scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

implementations/antigravity/.agents/skills/dare-design/SKILL.md · 194 lines

How it starts

The opening of the file, as written. The whole thing — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.

DARE Design Skill

Você é um especialista em planejamento e análise de requisitos. Seu objetivo é transformar a ideia inicial do usuário em um documento de Design estruturado que servirá como base para as próximas fases do Método DARE.

Quando usar esta skill

Usuário descreve uma nova feature ou projeto
Precisa-se clarificar requisitos antes de arquitetar
Necessário documentar escopo e restrições
Primeira fase do Método DARE

Equivalente no terminal: dare design "<description>" --ai

Como usar

Passo 1: Entender a Ideia

Leia cuidadosamente o que o usuário solicitou. Identifique:

O objetivo principal
Funcionalidades esperadas
Contexto do projeto
Restrições implícitas

Se dare design --interactive emitiu a seção ## Perguntas de Planejamento (Analyst/PM) no DESIGN.md, leia esse bloco.

Passo 1b: Planejamento leve (Analyst → PM)

Se o bloco de questionário existir, conduza 1 passagem sequencial (sem runtime multi-agente):

Analyst — uma rodada sobre escopo, ambiguidades e lacunas.
PM — uma rodada sobre requisitos e critérios de aceite.

Ordem sequencial; sem message pool, sem loop de troca. Inferências 🟡; lacunas 🔴; fatos do CLI 🟢.

Passo 2: Fazer Perguntas (se necessário)

Se algo não estiver claro, pergunte ao usuário:

Qual é o escopo exato?
Quem são os usuários?
Quais são as prioridades?
Há restrições técnicas?

Passo 3: Integrar Segurança (OWASP)

Sempre adicione requisitos de segurança:

Autenticação/Autorização
Proteção contra força bruta
Validação de entrada
Criptografia de dados sensíveis
Rate limiting

Passo 4: Gerar o Design

Crie um documento DARE/DESIGN.md com a seguinte estrutura:

# Design: [Nome do Projeto]

## Visão Geral
[Descrição clara do projeto]

## Objetivos
- [Objetivo 1]
- [Objetivo 2]
- [Objetivo 3]

## Funcionalidades Principais
### Feature 1: [Nome]
- Descrição
- Casos de uso

### Feature 2: [Nome]
- Descrição
- Casos de uso

## Stack Técnica
- **Backend:** [Linguagem/Framework]
- **Frontend:** [Framework]
- **Banco de Dados:** [BD]
- **Containerização:** Docker

## Requisitos Não-Funcionais
### Segurança
- Autenticação: [Tipo]
- Criptografia: [Tipo]
- Rate Limiting: Sim/Não
- Validação: Estrita

### Performance
- Tempo de resposta: [ms]
- Escalabilidade: [Tipo]

### Confiabilidade
- Uptime: [%]
- Backup: [Frequência]

## Restrições
- [Restrição 1]
- [Restrição 2]

## Fora do Escopo (v1.0)
- [Feature não incluída]
- [Feature não incluída]

## Próximas Etapas
1. Revisar e aprovar este Design
2. Executar `/generate-blueprint DARE/DESIGN.md`
3. Continuar com o Método DARE

Read the full file on GitHub · 194 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

3d ago First seen · 194 lines · 48 tokens per session scan A f52c9ef6ad39

Subscribe to this mod's changes

dare-design is a skill published in the GitHub repository dewtech-technologies/dare-method (5 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 1,417 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Planning agentic-engineering ai-agents ai-assisted-development ai-coding anthropic claude

write-test-plan

Generate a QA/UAT test plan from product specifications and task definitions, covering acceptance testing, integration flows, and exploratory testing. Unit tests are out of scope (handled by write-unit-tests skill).

andresharpe/dotbot · 43 tokens

implement-telegram-bot

Implement Telegram bot interactions with command handlers, message parsing, and inline keyboards for conversational interfaces.

andresharpe/dotbot · 23 tokens

setup-background-job

Set up scheduled background jobs using Quartz.NET with proper configuration, error handling, and dependency injection.

andresharpe/dotbot · 22 tokens

write-unit-tests

Write comprehensive unit tests with proper setup, assertions, and coverage of happy paths, edge cases, and error scenarios.

andresharpe/dotbot · 26 tokens

blazor-component-design

Design Blazor components with proper parameter binding, event callbacks, lifecycle management, and render optimization. Use when creating new Blazor Server or WASM components, refactoring component hierarchies, implementing cascading values, or optimizing component rendering performance.

andresharpe/dotbot · 53 tokens

hedgehog-planning-intake

Use on any core for first-run planning intake — Phase 0 runs the vendored BMAD-METHOD planning shelf, shared by every core, and Phase 1 (mining 04-prd.md into intent records plus the Add-ons/sync-and-remote-entities decision) is full-stack-app's and pwa-app's shared procedure — identical mechanics, a different…

skyf0xx/hedgehog · 374 tokens