strat-init

name	strat-init
description	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.

Strategy Init

Initialize the project workspace for Pi Strategy.

Purpose

This skill replaces static workspace templates. It creates the live project state in .ai/strategy/ only when the user asks to adopt or initialize the strategy workflow.

Workflow

1. Load ../_shared/references/strategy.md and ../_shared/references/artifact-conventions.md and apply language policy, core rules, and update conventions.
2. Inspect the current project lightly:
   • existing .ai/strategy/ files;
   • existing .ai/steering/ files;
   • README or package files only if useful for naming/context.
3. Create missing directories:
   • .ai/strategy/
   • .ai/strategy/signal/
   • .ai/strategy/offer/
   • .ai/strategy/gtm/
   • .ai/strategy/handoff/
   • .ai/steering/ when steering docs are requested or useful.
4. Create .ai/strategy/index.md if it does not exist.
5. If .ai/strategy/index.md exists, preserve useful existing content and update only missing sections.
6. Never overwrite existing .ai/strategy/* or .ai/steering/* files; propose a diff-style update and ask approval when replacing meaningful content.
7. When updating existing files, include an Update Notes section summarizing deltas.
8. Offer to create recommended steering docs under .ai/steering/ from the package templates, but do not overwrite existing steering docs without user approval.
9. Recommend the next skill, usually /skill:strat-market-signal.

Default index template

# Strategy Index

## Pipeline Status

- [ ] Market Signal
- [ ] User Context
- [ ] Problem / Outcome
- [ ] Product Offer
- [ ] Unique Mechanism
- [ ] MVP Scope
- [ ] Proof System
- [ ] Message System
- [ ] Acquisition Path
- [ ] Strategy Brief

## Current Decision

## Key Assumptions

## Open Questions

## Next Step

Optional steering docs

Recommended steering docs:

• .ai/steering/product-principles.md
• .ai/steering/marketing-principles.md
• .ai/steering/offer-principles.md
• .ai/steering/mvp-principles.md
• .ai/steering/acquisition-principles.md
• .ai/steering/anti-patterns.md
• .ai/steering/decision-rules.md
• .ai/steering/brand-voice.md

Use package-level templates/steering/*.md as examples when available.

Output

Common outputs:

• .ai/strategy/index.md
• .ai/strategy/signal/
• .ai/strategy/offer/
• .ai/strategy/gtm/
• .ai/strategy/handoff/
• optional .ai/steering/*.md

Output quality checklist

• Workspace directories exist.
• index.md exists with pipeline checklist.
• Existing content is preserved.
• No accidental overwrite happened.
• Next skill is recommended.

Critical rules

• Do not create strategy artifacts such as market-signal.md, product-offer.md, or strategy-brief.md in this skill unless the user explicitly asks for seeded placeholders.
• Do not create downstream deliverables, UI, implementation code, or presentation direction.
• Do not overwrite existing .ai/strategy/ or .ai/steering/ content without reviewing it first.
• Keep initialization minimal; strategy decisions belong to the pipeline skills.