pitch

Evaluates raw product ideas through a six-question kill gate producing build, kill, or park verdicts.

2|Updated Jul 24, 2026
One-click install
npx skills add https://github.com/konstantinos-malavazos/claude-code-playbook --skill pitch-konstantinos-malavazos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pitch
Source: https://github.com/konstantinos-malavazos/claude-code-playbook/tree/main/templates/skills/pitch
Command: npx skills add https://github.com/konstantinos-malavazos/claude-code-playbook --skill pitch-konstantinos-malavazos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Solo builders often commit weeks to ideas that were never worth building. This Skill runs a structured one-hour kill gate that forces a raw idea through six questions, two independent cold research searches, and an anonymised third-party judge, ending in a recorded verdict — build, kill, or park — instead of an open-ended conversation. ## Core Features & Use Cases - Six-question kill gate: Questions asked one at a time, with question zero classifying the idea (novelty, execution, or building-itself) to arm the right hard kills and brief the search agents. - Cold research subagents: Two /research subagents search whether the idea already exists and whether the hard part is tractable, deliberately kept unaware of the user's enthusiasm to avoid mirroring bias. - Three mechanical hard kills: No first version, already-exists-and-is-good, and the-hard-part-is-the-whole-project fire without weighing or appeal. - Anonymised pitch-judge: A case file with attribution stripped and verdict order randomised is judged independently to break ties or override false approvals. - Use Case: You have a side-project idea and no repo or spec. Run the gate; if it survives, the Skill creates a private repo, seeds issue #1 with the project map, and hands off to charting. If killed, the reason is recorded in a private ideas file for future reference. ## Quick Start Ask the assistant to run the pitch skill on your raw idea, for example: "I have an idea for a CLI tool that converts meeting notes into Jira tickets — pitch this and tell me if it is worth building."

Frequently Asked Questions about pitch

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

FAQPage Schema
How do I evaluate whether a side project idea is worth building?

Run the pitch kill gate: six questions asked one at a time, two cold research searches on existing solutions and the hard part, then a verdict of build, kill, or park. The whole process takes about an hour and ends with a recorded decision.

How does the pitch skill decide to kill an idea?

Three hard kills fire mechanically: no smallest buildable version after pushback, the idea already exists and is good (novelty claims only), or the hard part is the entire project with no cheap way to test it. A fired hard kill cannot be overridden by anyone.

When should I not use the pitch skill?

Do not use it for work that already has a ticket, a repo, or a spec — that work enters through /start-ticket instead. Pitch is only for raw ideas with nothing built or assigned yet.

What happens when an idea gets a build verdict?

The skill confirms a repo name with you, creates a private repo, seeds issue #1 with a project map including the smallest version and the hard part as the first research ticket, and records the idea as built in the ideas file. Charting runs in the next session.

What is the difference between park and kill verdicts?

Park requires a concrete trigger that will end and be noticed, like "after the house move". Vague conditions like "when I have more time" convert to a kill. Both are recorded in the ideas file with reasons.