Skill

ship

Generates ADRs and plans from technical brainstorms or outlines from conceptual ones after STRESS phase. Spawns subagents for inline mermaid diagrams; detects IaC for verification commands.

Mermaid

Terraform

documentation

npx claudepluginhub jesgarram/arete --plugin arete

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Transform brainstorm decisions into retrievable artifacts that serve as **boundary objects** — specific enough for engineers to implement from, clear enough for non-engineers to understand trade-offs.

Supporting Assets

references/ADR.mdreferences/Outline.mdreferences/Plan.mdreferences/tdd-app.mdreferences/tdd-iac.mdreferences/tdd-load.md

SKILL.md

Similar Skills

writing-design-plans

159

Appends validated designs from brainstorming to docs/design-plans/ Markdown files, fills summary and glossary placeholders, specifies module structures, components, and contracts for archival git commits.

ed3d-plan-and-execute

architecture

Creates Architecture Decision Records (ADRs) in MADR format, arc42 documentation, and plan-context.md as context bridge to Claude Code. For architecture, tech stack, system design, or technical structuring.

9 files

digital-innovation-agents

ce-brainstorm

Explores feature ideas and requirements via collaborative dialogue, then generates a right-sized requirements document for planning. Use for vague requests, brainstorming, or scoping ambiguous problems.

atv-starter-kit

Stats

Stars32

Forks6

Last CommitMar 8, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Ship

Transform brainstorm decisions into retrievable artifacts that serve as boundary objects — specific enough for engineers to implement from, clear enough for non-engineers to understand trade-offs.

Flow

Detect track: Technical → ADR + Plan | Conceptual → Outline
Detect domain: IaC → load references/tdd-iac.md
Generate documents from brainstorm content
Identify sections with component interactions → spawn parallel architect subagents
Inject returned mermaid inline (max 3 diagrams per doc)
Add frontmatter (problem:, date:) and save

Output

Track	Document	Location	Naming
Technical	ADR	`context/exports/`	`[slug]-adr-YYYY-MM-DD.md`
Technical	Plan	`context/plans/`	`[slug]-plan-YYYY-MM-DD.md`
Conceptual	Outline	`context/exports/`	`[slug]-outline-YYYY-MM-DD.md`

Technical ADR + Plan cross-reference each other via frontmatter.

Templates

ADR: references/ADR.md - the why and what
Plan: references/Plan.md - the how
Outline: references/Outline.md - conceptual track

Domain Detection (Progressive Disclosure)

Detect domain from brainstorm content and load additional references.

Domain	Context Indicators	Reference
IaC	terraform, infrastructure, resource, module, azure, aws, gcp, cloud, deploy, provision	`references/tdd-iac.md`

When IaC domain detected:

Load references/tdd-iac.md for verification patterns
Include IaC-specific verification commands in plan tasks
Prefer executable commands over natural language descriptions

Plan Generation (Technical Track)

Each implementation task MUST include verification:

### Task N: [Title]

**Files:** `path/to/file`

[Description]

**Verify:** [Command or check]
**Expect:** [Expected outcome]
**Depends on:** [Previous tasks if any]

Verification Guidelines

Prefer commands - Use executable verification commands when possible
Natural language fallback - Acceptable when commands not feasible
Cross-component tests - Attach to later component, set dependencies
Definition of Done - Consolidate all verifications in final section

IaC-Specific Verifications

When IaC detected, use patterns from references/tdd-iac.md:

After resource creation: State assertion + existence check
After networking changes: Connectivity check
After secret/config changes: Integration test
Before completion: Policy validation

Diagram Generation

Spawn architect subagent for sections with component interactions.

Trigger keywords: service, database, API, cache, queue, client, calls, sends, flows

Process: Identify sections → spawn parallel subagents (section title + text) → inject returned mermaid or discard NO_DIAGRAM