원클릭으로 Manus에서 모든 스킬 실행

strat-acquisition-path

스타1

포크0

업데이트2026년 5월 15일 14:11

Chooses the correct next action for prospects based on offer readiness, awareness, trust, friction, price, urgency, and MVP maturity. Use after message-system to define CTA and acquisition path.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

felipefontoura

felipefontoura/pi-strategy

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Acquisition Path

Define whether the prospect should buy, test, join waitlist, book demo, apply, request diagnostic, DM, subscribe, or consume a lead magnet.

Workflow

Load ../_shared/references/strategy.md, ../_shared/references/artifact-conventions.md, and ../_shared/references/quality-gates.md.
Read .ai/strategy/signal/*, .ai/strategy/offer/*, and .ai/strategy/gtm/message-system.md.
Evaluate offer readiness, buyer awareness, trust required, friction level, price, urgency, and MVP maturity.
Choose one recommended path and explain why not the others.
Add a compact mapping table: Channel -> CTA -> Measurement Event.
Define one next experiment with hypothesis and cutoff criterion.
Save .ai/strategy/gtm/acquisition-path.md.

Output template

# Acquisition Path

## Offer Readiness

## Buyer Awareness

## Trust Required

## Friction Level

## Recommended Path

Options: Direct checkout, Free trial, Freemium, Waitlist, Early access, Book demo, Diagnostic, Application, WhatsApp / DM, Newsletter, Lead magnet

## Primary CTA

## Secondary CTA

## Why This Path

## Why Not Other Paths

## Follow-Up Mechanism

## Measurement Events

## Conversion Risks

## Next Experiment

## Assumptions

## Open Questions

Decision rules

Hot user: checkout, trial, or demo.
Warm user: diagnostic, application, or early access.
Cold user: newsletter, lead magnet, or content.
SaaS validation: waitlist + demo, early access, or free trial.
High-ticket: diagnostic, application, or call.
Community: waitlist, application, or pilot cohort.

Output quality checklist

CTA matches buyer readiness and trust.
Primary vs secondary CTA are coherent.
Measurement events are explicit.
Channel/CTA/event mapping is included.
Next experiment has hypothesis + cutoff.

Critical rules

Lead magnet is optional, not mandatory. Do not create downstream deliverables or implementation code.

이 저장소의 다른 Skills

같은 저장소

strat-brief

felipefontoura/pi-strategy

Consolidates all Pi Strategy artifacts into the final handoff file .ai/strategy/handoff/strategy-brief.md for downstream SDD, build, or go-to-market packages. Use after acquisition-path.

2026-05-151

strat-init

felipefontoura/pi-strategy

Initializes the Pi Strategy workspace in a project by creating .ai/strategy directories, index.md, and optional .ai/steering guidance. Use before running the strategy pipeline in a new or existing project.

2026-05-151

strat-market-signal

felipefontoura/pi-strategy

Identifies whether a raw product, SaaS, devtool, community, course, method, or service idea has enough reachable market signal to continue. Use at the beginning of Pi Strategy before user, offer, MVP, or build work.

2026-05-151

strat-message-system

felipefontoura/pi-strategy

Turns offer, mechanism, MVP, and proof into clear technical messaging: positioning, promise, pillars, hooks, claims, objection matrix, CTA options, FAQ seeds, words to use/avoid, and a skeptical developer explanation. Use after proof-system.

2026-05-151

strat-mvp-scope

felipefontoura/pi-strategy

Defines the smallest MVP or deliverable capable of proving the offer and mechanism. Use after product-offer and unique-mechanism, before proof, messaging, acquisition, downstream deliverables, or build planning.

2026-05-151

strat-problem-outcome

felipefontoura/pi-strategy

Maps the surface problem, deeper problem, cost of inaction, failed attempts, desired outcomes, transformation gap, and priority problem. Use after market signal and user context, before offer creation.

2026-05-151

name	strat-acquisition-path
description	Chooses the correct next action for prospects based on offer readiness, awareness, trust, friction, price, urgency, and MVP maturity. Use after message-system to define CTA and acquisition path.

Acquisition Path

Define whether the prospect should buy, test, join waitlist, book demo, apply, request diagnostic, DM, subscribe, or consume a lead magnet.

Workflow

Load ../_shared/references/strategy.md, ../_shared/references/artifact-conventions.md, and ../_shared/references/quality-gates.md.
Read .ai/strategy/signal/*, .ai/strategy/offer/*, and .ai/strategy/gtm/message-system.md.
Evaluate offer readiness, buyer awareness, trust required, friction level, price, urgency, and MVP maturity.
Choose one recommended path and explain why not the others.
Add a compact mapping table: Channel -> CTA -> Measurement Event.
Define one next experiment with hypothesis and cutoff criterion.
Save .ai/strategy/gtm/acquisition-path.md.

Output template

# Acquisition Path

## Offer Readiness

## Buyer Awareness

## Trust Required

## Friction Level

## Recommended Path

Options: Direct checkout, Free trial, Freemium, Waitlist, Early access, Book demo, Diagnostic, Application, WhatsApp / DM, Newsletter, Lead magnet

## Primary CTA

## Secondary CTA

## Why This Path

## Why Not Other Paths

## Follow-Up Mechanism

## Measurement Events

## Conversion Risks

## Next Experiment

## Assumptions

## Open Questions

Decision rules

Hot user: checkout, trial, or demo.
Warm user: diagnostic, application, or early access.
Cold user: newsletter, lead magnet, or content.
SaaS validation: waitlist + demo, early access, or free trial.
High-ticket: diagnostic, application, or call.
Community: waitlist, application, or pilot cohort.

Output quality checklist

CTA matches buyer readiness and trust.
Primary vs secondary CTA are coherent.
Measurement events are explicit.
Channel/CTA/event mapping is included.
Next experiment has hypothesis + cutoff.

Critical rules

Lead magnet is optional, not mandatory. Do not create downstream deliverables or implementation code.