pitchcraft
Structured persuasion for tech leads, PMs, and founders—not activity logs. Five scenarios (kickoff, status update, wrap-up, investor pitch, solution selling) on one 5-part framework (Hook→Context→Proposal→Evidence→Ask). AI prompts for missing materials and audience context; pre-submit checklist. Claude Code plugin; Cursor, Codex, and chat via prompts.
npx skills add moshuying/pitchcraft --skill pitchcraft --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
**Languages:** English (this file) · 简体中文 → `SKILL.zh-CN.md` # Persuasive briefings · Workflow ## Essence This is not report writing—it is **persuasion**. In every scenario you do the same thing: > In limited time, help a specific audience understand context, trust your judgment, and provide the support you need. ## Users & scenarios | Role | Scenarios | Audience | |---|---|---| | Tech lead / engineering manager | Kickoff, milestone review, wrap-up | Business leaders, CTO, PMO | | PM / product lead | Quarterly review, annual summary, requirements review | Director, VP | | Founder / business owner | Investor pitch | Investors, partners | | Pre-sales / solutions | Solution selling | Customer execs, technical evaluators | --- ## Core: 5-part persuasion framework All briefing types share one backbone; section emphasis differs. ``` Part 1 · Hook → Why should they keep listening? → Opportunity / pain / urgency Part 2 · Context → What is the situation? → What we have done and what we have Part 3 · Proposal → What we will do / did? → Scope, path, pace Part 4 · Evidence → Why we can succeed / succeeded? → Data, moat, team, cases Part 5 · Ask → What do we need from them? → Decision / resourc
- Essence
- Users & scenarios
- Core: 5-part persuasion framework
- Briefing types & templates
- Project kickoff
- Status update
- Wrap-up / annual review
- Investor pitch
- Solution selling
- Writing rules
- 1. Their concerns first, your story second
- 2. Risks need judgment
- 3. Acknowledge peer teams first
- 4. Metrics need source and definition
What does the pitchcraft skill do?
Structured persuasion for tech leads, PMs, and founders—not activity logs. Five scenarios (kickoff, status update, wrap-up, investor pitch, solution selling) on one 5-part framework (Hook→Context→Proposal→Evidence→Ask). AI prompts for missing materials and audience context; pre-submit checklist. Claude Code plugin; Cursor, Codex, and chat via prompts.
How do I install it?
Run `npx skills add moshuying/pitchcraft --skill pitchcraft --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From moshuying/pitchcraft, a repository with 184 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.