shapeuppitching
Use when: writing, reviewing, or refining Shape Up pitches for drafting, completeness critique, or betting table preparation.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Use when: writing, reviewing, or refining Shape Up pitches for drafting, completeness critique, or betting table preparation.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when: reviewing .prompt.md, .agent.md, SKILL.md, or .instructions.md files for contradictions, ambiguity, persona consistency, cognitive load, coverage gaps, and composition conflicts.
Use when: checking xanadAssistant workspace health, install status, repair reasons, or lockfile validity before proposing install, update, repair, or restore operations.
Use when: designing or reviewing CI/CD pipelines, GitHub Actions, stage design, environment gates, or artifact discipline.
Use when: writing or reviewing Dockerfiles, container images, multi-stage builds, layer caching, or image security.
Use when: writing or reviewing Infrastructure as Code for naming, state management, modularity, and drift detection.
Use when: reviewing DevOps changes for pipeline safety, secret hygiene, permissions, rollback, and deployment risk.
| name | shapeupPitching |
| description | Use when: writing, reviewing, or refining Shape Up pitches for drafting, completeness critique, or betting table preparation. |
| type | reference |
| version | 1.0 |
| license | MIT |
Skill metadata: version "1.0"; tags [shapeup, pitching, product-management]; recommended tools [].
Shape Up pitches are the unit of work proposed for a betting table. A pitch answers five questions before any cycle time is committed.
shapeupBettingshapeupCycleWork| Element | What it covers |
|---|---|
| Problem | The raw customer pain or business friction — not a solution in disguise. |
| Appetite | How much time the team is willing to spend: S (1-2 weeks), M (4 weeks), or L (6 weeks). |
| Solution | A concrete enough sketch to convey the approach — fat-marker sketch, breadboard, or short prose. Enough to bet on, not a full spec. |
| Rabbit holes | Specific technical or design traps that would blow the appetite if unaddressed. |
| No-gos | Explicit things the solution will not do — used to define the boundary of the bet. |
Before presenting to the betting table, confirm:
Use these prefixes when giving pitch feedback:
problem: — the problem statement is unclear, hidden, or a solution in disguiseappetite: — the appetite is missing, unjustified, or inconsistent with scopescope: — the solution exceeds the stated appetite or introduces unbounded workrabbit-hole: — a likely rabbit hole is unaddressedno-go: — scope boundary is unclear or missingnit: — minor wording or formatting issue