Initial commit: antigravity-ipa-workflow
This commit is contained in:
131
skills/lean-analyst/SKILL.md
Normal file
131
skills/lean-analyst/SKILL.md
Normal file
@@ -0,0 +1,131 @@
|
||||
---
|
||||
name: lean-analyst
|
||||
description: Lean Software Development methodology framework — provides MVP definition criteria, feature prioritization matrix, assumption validation methods, and phase breakdown rules. Activated automatically by lean, lean-user-research, and lean-analyze-usage. Trigger phrases: "lean methodology", "mvp framework", "feature prioritization lean".
|
||||
---
|
||||
|
||||
## Overview
|
||||
|
||||
Provides Lean Software Development methodology for analyzing ideas and defining MVPs. Core reference for the lean, lean-user-research, and lean-analyze-usage skills.
|
||||
|
||||
## When to Use
|
||||
|
||||
- Invoked automatically during lean analysis
|
||||
- When applying lean methodology to MVP definition
|
||||
- When prioritizing features using value vs effort matrix
|
||||
- When planning phase breakdown for a project
|
||||
|
||||
## Don't Use When
|
||||
|
||||
- IPA documentation already exists and implementation is ready to begin
|
||||
- Only a quick command reference is needed
|
||||
|
||||
## The 7 Lean Principles (Mary Poppendieck)
|
||||
|
||||
| # | Principle | Application |
|
||||
|---|-----------|-------------|
|
||||
| 1 | Eliminate Waste | Only build features with proven user value |
|
||||
| 2 | Amplify Learning | Validate assumptions early, iterate fast |
|
||||
| 3 | Decide as Late as Possible | Keep options open until necessary |
|
||||
| 4 | Deliver as Fast as Possible | Smallest valuable increment first |
|
||||
| 5 | Empower the Team | Trust team decisions |
|
||||
| 6 | Build Integrity In | Quality from start |
|
||||
| 7 | See the Whole | Optimize whole system, not parts |
|
||||
|
||||
## 7 Wastes in Software Development
|
||||
|
||||
| Waste | How to Eliminate |
|
||||
|-------|------------------|
|
||||
| Partially Done Work | Smaller batches, complete before starting new |
|
||||
| Extra Features | Validate need before building |
|
||||
| Relearning | Document decisions (D-xx in SRD) |
|
||||
| Handoffs | Cross-functional teams |
|
||||
| Task Switching | Focus on one thing at a time |
|
||||
| Delays | Remove blockers proactively |
|
||||
| Defects | Quality built in, early testing |
|
||||
|
||||
## MVP Definition
|
||||
|
||||
```
|
||||
MVP = Minimum + Viable + Product
|
||||
|
||||
Minimum: Smallest feature set
|
||||
Viable: Actually solves the problem
|
||||
Product: Can be used by real users
|
||||
```
|
||||
|
||||
MVP Checklist:
|
||||
- [ ] Solves a real user problem
|
||||
- [ ] Has clear success metrics
|
||||
- [ ] Can be built in reasonable time
|
||||
- [ ] Assumptions are identified
|
||||
- [ ] Validation plan exists
|
||||
|
||||
## Feature Prioritization
|
||||
|
||||
| Priority | Criteria | Action |
|
||||
|----------|----------|--------|
|
||||
| P1 | Core value, must have for launch | Build in MVP |
|
||||
| P2 | Important, enhances value | Build after MVP validation |
|
||||
| P3 | Nice to have | Defer, validate need first |
|
||||
| P4 | Future consideration | Document, don't build |
|
||||
|
||||
## Assumption Validation Methods
|
||||
|
||||
| Type | Example | How to Validate |
|
||||
|------|---------|-----------------|
|
||||
| Problem | Users have this pain | User interviews |
|
||||
| Solution | Our approach works | Prototype testing |
|
||||
| Market | People will pay | Landing page test |
|
||||
| Technical | We can build it | Spike/POC |
|
||||
|
||||
## Phase Breakdown Rules
|
||||
|
||||
| Features | Recommended Phases |
|
||||
|----------|-------------------|
|
||||
| 1-3 P1 features | 1 phase |
|
||||
| 4-6 P1 features | 2 phases |
|
||||
| 7+ P1 features | 3+ phases (consider re-scoping) |
|
||||
|
||||
## Lean → IPA Mapping
|
||||
|
||||
| Lean Output | IPA Input |
|
||||
|-------------|-----------|
|
||||
| Problem Statement | SRD Section 2 (Objectives) |
|
||||
| MVP Features | SRD Section 4 (Feature List) |
|
||||
| Target Users | SRD Section 3 (User Roles) |
|
||||
| Assumptions | SRD Section 14 (Key Decisions) |
|
||||
| Out of Scope | SRD Section 2 (exclusions) |
|
||||
|
||||
## Data Analysis Integration
|
||||
|
||||
### Pre-Build (User Research)
|
||||
|
||||
| Method | When to Use |
|
||||
|--------|-------------|
|
||||
| Persona Development | Before lean |
|
||||
| Journey Mapping | Before ipa-bd |
|
||||
| Competitor Analysis | Before MVP definition |
|
||||
|
||||
### Post-Build (Usage Analytics)
|
||||
|
||||
| Method | When to Use |
|
||||
|--------|-------------|
|
||||
| Behavioral Analysis | After launch |
|
||||
| Funnel Analysis | Optimization phase |
|
||||
| Cohort Analysis | Growth phase |
|
||||
|
||||
## Workflow Integration
|
||||
|
||||
```
|
||||
lean-user-research → docs/USER_RESEARCH.md
|
||||
↓
|
||||
lean → MVP definition (data-informed)
|
||||
↓
|
||||
ipa-bd → UI_SPEC.md (with design rationale)
|
||||
↓
|
||||
Launch → Collect usage data
|
||||
↓
|
||||
lean-analyze-usage → Improvement insights
|
||||
↓
|
||||
lean [improvement] → Next iteration
|
||||
```
|
||||
Reference in New Issue
Block a user