A guide for turning rough thoughts, notes, or voice transcripts into organised documents such as one-page ideas, pitches, or product requirement documents (PRDs). It chooses the document type based on how developed the idea is.

Use it to shape an early idea, explain a problem and possible approach, or write detailed requirements for a team.

It removes the need to organise your thinking before you begin. It helps turn incomplete or contradictory input into a useful document for exploration, discussion, or implementation.

How kintecus/build configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to kintecus/build. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/kintecus/build/main/.claude/skills/ideation/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/kintecus/build

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/kintecus/build/ideation/github.svg)](https://agentmods.dev/skills/kintecus/build/ideation)

Your own site

<a href="https://agentmods.dev/skills/kintecus/build/ideation"><img src="https://agentmods.dev/badge/skills/kintecus/build/ideation/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/kintecus/build/ideation"><img src="https://agentmods.dev/badge/skills/kintecus/build/ideation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

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

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.1	$0.00067	$0.01006
Opus 5.5	$0.00027	$0.00402
Sonnet 5.5	$0.00013	$0.00201
Haiku 4.5	$0.00007	$0.00101

Measured 2mo ago against content hash bf8df417ba3f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ideation 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 2mo 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.

.claude/skills/ideation/SKILL.md · 97 lines

How it starts

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

Ideation

Transform unstructured thinking into the right document for its maturity level.

Phase 1: Intake

Accept whatever the user provides without judgment:

Scattered thoughts and half-formed ideas
Voice dictation transcripts
Bullet points mixed with rambling
Topic jumping, tangents, contradictions
"I'm not sure but maybe..." statements

The mess is the input. Don't ask for organization.

Acknowledge receipt and begin analysis. Do not ask for clarification yet.

Phase 2: Route

After intake, classify the input into one of five tracks. Consider:

How mature is the thinking? (vague hunch vs clear problem vs detailed solution)
What does the user need next? (validation vs alignment vs execution)
Who is the audience? (themselves vs team vs stakeholders)

Routing table

Signal	Track	Output
Vague idea, lots of "maybe", exploring whether something is worth pursuing	Exploring	One-pager
Clear problem, unclear solution, needs to figure out the approach	Shaping	Pitch (Shape Up style)
Approach is clear, needs detailed requirements for team execution	Specifying	PRD
Stuck between options, needs structured comparison	Deciding	Decision doc
Needs to explain or sell an idea to stakeholders	Communicating	Memo/proposal

Propose the route

Tell the user which track you've identified and why. Suggest the output type. Let them confirm or redirect.

Example: "This sounds like you're still exploring whether this is worth building. I'd suggest we shape this into a one-pager - problem, hypothesis, key assumptions - rather than jumping to a PRD. Want to go that direction, or do you need something more detailed?"

Do not proceed until the user confirms the track.

Phase 3: Interview

Conduct a targeted interview based on the selected track. Load the appropriate rubric from routing-rubrics.md.

Interview principles

Ask 2-3 questions at a time, max; target three rounds or less

Read the full file on GitHub · 97 lines

Files

What ships with it

6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

2mo ago First seen · 97 lines · 67 tokens per session scan A bf8df417ba3f

Subscribe to this mod's changes

ideation is a skill published in the GitHub repository kintecus/build (2 stars, last pushed 3mo ago), licensed MIT. It adds 67 tokens to every session and 1,006 once invoked, about $0.0003 per session on Opus 5.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 Writing and docs

ideation next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
ideationkintecus/build	Skill	2	3mo ago	MIT	A	67	Claude Code
imagegenopenai/codex	Skill	133k	yesterday	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	313k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	103	Claude Code

build: Skill for Claude Code