with one click
pi-strategy
pi-strategy contains 11 collected skills from felipefontoura, with repository-level occupation coverage and site-owned skill detail pages.
Skills in this repository
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.
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.
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.
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.
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.
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.
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.
Creates a product offer using the value equation from $100M Offers: dream outcome, perceived likelihood, time delay, effort/sacrifice, offer stack, risk reversal, pricing logic, naming, and one-liner. Use after problem/outcome.
Defines honest proof, missing proof, proof needed for claims, proof generated from the MVP, proof acquisition plan, supported claims, unsupported claims, and credibility risks. Use after MVP scope.
Defines the unique mechanism that explains why the offer works differently from the old way. Use after product-offer and before MVP scope.
Turns the selected market segment into a concrete user and buyer context: situation, workflow, alternatives, triggers, objections, language, needs, and fears. Use after strat-market-signal and before problem/outcome work.