ptp-brainstorming

Turns a change request into one recorded decision capsule with alternatives and assumptions.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/AlmogMaayan/ptp --skill ptp-brainstorming-almogmaayan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ptp-brainstorming
Source: https://github.com/AlmogMaayan/ptp/tree/main/skills/ptp-brainstorming
Command: npx skills add https://github.com/AlmogMaayan/ptp --skill ptp-brainstorming-almogmaayan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Planning sessions often stall on ambiguity, produce bloated multi-file design docs, or pad option lists with artificial alternatives. This Skill converts a change request into exactly one durable decision capsule, keeping the brainstorming step of a change pipeline focused and auditable. ## Core Features & Use Cases - Autonomous and interactive modes: In autonomous mode it resolves ambiguity by inspecting the repository and records assumptions with cited evidence; in interactive mode it asks only questions whose answers would change the decision, scope, or a contract. - Single-capsule output: Writes exactly one Markdown file (e.g. openspec/changes/<change-id>/brainstorm.md) with Decision, Alternatives, and Assumptions sections, replacing prior content on re-runs. - Material alternatives only: Compares options that differ in observable behavior, contract, risk, or blast radius, and states when only one direction is viable. - Use Case: Given a request like "add a retry to the telemetry sink write path", the Skill inspects the sink code, picks a reasonable retry count, cites the file as evidence, and writes the capsule without pausing for user input. ## Quick Start Ask the agent to run the ptp brainstorming step in autonomous mode for your change request and write the decision capsule to the change's brainstorm.md path.

Frequently Asked Questions about ptp-brainstorming

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run the brainstorming step of a change pipeline autonomously?▼

Declare mode: autonomous or declare nothing, since autonomous is the default. The Skill resolves ambiguities by inspecting the repository, records each assumption with cited evidence in the capsule, and never pauses for user questions or approvals.

What output does the brainstorming step produce?▼

It writes exactly one Markdown capsule at the caller-named path, typically openspec/changes/<change-id>/brainstorm.md. The default shape has Decision, Alternatives, and Assumptions sections, and a re-run fully replaces the file rather than appending history.

When does interactive mode ask the user questions?▼

Interactive mode asks only when different answers would change the decision, scope, or a contract. It never asks what the repository already answers, never sends questionnaires, and requests approval once on the decision rather than per section.

How are alternatives evaluated during brainstorming?▼

Only material alternatives are compared, meaning options that differ in observable behavior, contract, risk, or blast radius. When exactly one direction is viable, the capsule states that with the reason instead of inventing options to reach a count.

What are the limitations of the brainstorming step?▼

It does not carry the full design, implementation plan, or task list, which belong to design.md and the plan-writing step. It also never runs git commands, writes secondary doc copies, or invokes implementation skills.