v2.0.0 — Competitive Intelligence System Upgrade

The CI system went from a monolithic skill to a modular, structured intelligence system where context compounds across every mode.

- Split /analyze-competitors from one 205-line file into a router (38 lines) + 6 workflow modules (landscape, deep-dive, synthesis, monitoring, guide, quality-rules)
- Each module loads on demand. Router detects the mode, reads the right file.

- 4 competitor types (Direct, Indirect, Substitute, Potential) with identification techniques per type
- Structured competitor profiles with fixed fields
- Source and confidence tagging on every data point
- Positioning map with axis selection guidance
- Coverage assessment flagging what's verified vs shallow
- New template (template/competitive-landscape.md) with 7 sections

- Profile Summary at the top (structured fields that landscape uses for pre-population)
- Source and confidence tagging per claim (High/Med/Low)
- Competitor type classification (D/I/S/P) in frontmatter
- Seamless data flow into landscape universe table

- Evidence base structured around 6 categories: problem space, who's affected, competitive alternatives, our advantage, timing, risks
- Top 3 opportunities as "we should" statements grounded in evidence
- Coverage assessment: what's solid, shallow, missing, recommended next steps
- Owns the Strategic Insights section of context/competitors.md

- Run /analyze-competitors with no arguments to see where you are and what to do next
- Reads context state, assesses CI maturity, recommends the specific next step
- Adapts to context: empty → onboard, no landscape → map the market, deep dives exist → synthesize

- Market section added to company.md (market definition, JTBD, ICP segments, scope)
- Onboarding flow reordered: company → market → competitors → personas → product
- Market questions added to follow-up step

Context IS the chain. Each mode reads what others wrote to context/competitors.md:
- Deep dives feed landscape (pre-population via Profile Summary)
- Landscape feeds synthesis (market structure + profiles)
- Synthesis produces Strategic Insights section
- Monitoring tracks drift
- No orchestration engine needed

Repo cleanup: remove setup/, fix gitignore, add missing files

- Remove obsolete setup/ directory (no longer needed)
- Add context/*/ to .gitignore (prevents committing deep dives, teardowns)
- Commit investor-update style template
- Add /product-teardown to AGENTS.md command list
- Add issue template config (disable blank issues, link to discussions)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Update analyze-competitors to v1.4.0: synthesis mode, audience handli…

…ng, edge case fixes

Promotes synthesis to its own mode with staleness checks and cross-cutting analysis guidance.
Adds audience/tone section, duplicate detection, empty-directory fallbacks, paywall guidance.
Drops redundant frontmatter status field from template. Restructures into four top-level workflows.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Add /product-teardown to README skills table and Codex section

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

New structured competitive deep dive template, skill v1.1.0

Add Codex entry point and support

Add version field to all skill files

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Move /onboard out of skills table into getting started

Onboarding is setup, not a PM skill. Keep it accessible but don't count it
alongside the 9 core workflow skills.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>