メニュー
Use when outlining, reviewing, or rehearsing a Guochuang pitch deck, project-book presentation, slide narrative, or visual evidence sequence.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/leewayworks/guochuang-gps --skill deckコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
Use when a Guochuang project needs its customer, market, transaction, pricing, finance, delivery, scale, risk or social-value logic examined.
Use when simulating Guochuang roadshows, expert questions, rebuttals, speaker scripts, or a final readiness drill for school, provincial, or national rounds.
Use when collecting, classifying, validating or cross-checking sources for Guochuang claims across documents, data, tests, IP, customer, finance and team records.
| name | deck |
| description | Use when outlining, reviewing, or rehearsing a Guochuang pitch deck, project-book presentation, slide narrative, or visual evidence sequence. |
Apply the shared policies in gps-common. When saving a Markdown report, use the common project-name rule with topic PPT.
Design the deck as a sequence of reviewer decisions. Each slide needs one conclusion, one visual job and one evidence pointer.
A common technical or venture spine is:
value in one sentence -> real problem -> field finding -> intervention -> mechanism -> baseline and metric -> validation -> user or scene -> alternatives -> IP and student work -> customer and economics -> growth -> social value -> ask.
Change the order when the track demands it. For an industry project, make the chain visible: enterprise question -> response -> demonstrator -> expert questions. For red-tour, show participation and beneficiary change early.
For each page fill: no, purpose, headline, visual, evidence_ids, speaker cue, risk and cut priority.
The headline should state the conclusion, not the topic. Put units, sample size, date and source beside a number. Keep project-book, slide and spoken figures identical. Label image-only pages visual review required; missing extracted text is not proof that a page is empty.
Prepare three versions:
Never cut the only baseline, limitation or student-contribution evidence. Timing, page count, font and effects are local rules until the 2026 evaluation notice or a school or provincial notice confirms them.
Check headline clarity, legibility, source and date, units, number consistency, ownership, privacy, transitions, screen readability and unsupported superlatives. End with the two claims the team wants the reviewer to remember and the evidence that supports each.
See references/slide-patterns.md for historical patterns.