App Growth Templates

Artifact templates — grow-app

by wondelai · MIT license · ★ 2,235 on GitHub · updated Sep 10

Artifact templates — grow-app cover

Skeletons this metaskill creates in the user's docs/ folder.

# Artifact templates — grow-app

Skeletons this metaskill creates in the user's docs/ folder. Extend-only artifacts (CUSTOMER.md, EXPERIMENTS.md, DESIGN.md, OFFER.md, and the optional MARKETING.md / STRATEGY.md) are governed by the section headings named in each phase — read the existing file, add or update your sections, preserve everyone else's. The two skeletons below (METRICS.md, PRODUCT.md) are the files grow-app most often creates from scratch; copy them verbatim.

## Tracker: docs/GROW-APP-PLAN.md

Create this on first run (Intake). Phase rows are pre-filled; fill Status and Date as the journey advances.

```markdown
# Grow an App Plan

## Context
Intake answers, date started, project specifics.

## Phase Status
| Phase | Skill | Status | Artifact | Date |
|---|---|---|---|---|
| 1. Habit loop | hooked-ux | pending | PRODUCT.md | |

Overview

Skeletons this metaskill creates in the user's docs/ folder. Extend-only artifacts (CUSTOMER.md, EXPERIMENTS.md, DESIGN.md, OFFER.md, and the optional MARKETING.md / STRATEGY.md) are governed by the section headings named in each phase — read the existing file, add or update your sections, preserve everyone else's. The two skeletons below (METRICS.md, PRODUCT.md) are the files grow-app most often creates from scratch; copy them verbatim.

Manual install (npx, ZIP)
Claude Codenpx skills add wondelai/skills --skill artifact-templates-grow-app -g -a claude-code
Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • artifact-templates.md2.7 KB
Read artifact-templates.md here
wondelai/main1 file
artifact-templates.md
Show the full text90 lines
artifact-templates-grow-app/artifact-templates.md90 lines · 2.7 KB

Artifact templates — grow-app

Skeletons this metaskill creates in the user's docs/ folder. Extend-only artifacts (CUSTOMER.md, EXPERIMENTS.md, DESIGN.md, OFFER.md, and the optional MARKETING.md / STRATEGY.md) are governed by the section headings named in each phase — read the existing file, add or update your sections, preserve everyone else's. The two skeletons below (METRICS.md, PRODUCT.md) are the files grow-app most often creates from scratch; copy them verbatim.

Tracker: docs/GROW-APP-PLAN.md

Create this on first run (Intake). Phase rows are pre-filled; fill Status and Date as the journey advances.

# Grow an App Plan

## Context
Intake answers, date started, project specifics.

## Phase Status
| Phase | Skill | Status | Artifact | Date |
|---|---|---|---|---|
| 1. Habit loop | hooked-ux | pending | PRODUCT.md | |
| 2. Activation | improve-retention | pending | PRODUCT.md | |
| 3. Continuous discovery | continuous-discovery | pending | PRODUCT.md, CUSTOMER.md | |
| 4. Lean UX experiments | lean-ux | pending | EXPERIMENTS.md | |
| 5. Empowered team | inspired-product | pending | PRODUCT.md | |
| 6. One metric that matters | lean-analytics | pending | METRICS.md | |
| 7. Microinteractions | microinteractions | pending | DESIGN.md | |
| 8. Intrinsic motivation | drive-motivation | pending | PRODUCT.md | |
Statuses: pending · in-progress · awaiting-evidence · done · deferred: <reason> · skipped: <reason>

## Key Decisions
| Date | Phase | Decision | Rationale |
|---|---|---|---|

## Next Actions
- [ ] action (owner, due)

docs/METRICS.md

Created in Phase 6 (lean-analytics). Creates: improve-business, grow-app.

# Metrics

## Stage & One Metric That Matters
OMTM · counter-metric · why now.

## KPI Definitions
| Metric | Definition | Actionable ratio? | Owner |
|---|---|---|---|

## Baselines & Targets
| Metric | Baseline (date) | Target | Line in the sand (miss response) |
|---|---|---|---|

## Funnel
| Stage | Conversion | Benchmark | Bottleneck? |
|---|---|---|---|

## Cohort Notes

docs/PRODUCT.md

Extended across Phases 1, 2, 3, 5, and 8; create it here if the project has no PRODUCT.md yet. Creates: create-app, create-business. Extends: grow-app, improve-app.

# Product

## Vision
One paragraph.

## MVP Definition
Type, scope, what it deliberately excludes.

## Outcome Roadmap
| Outcome / problem | Job served | Priority | Status |
|---|---|---|---|

## Opportunity Solution Tree Notes

## Hook Model
Trigger → Action → Variable reward → Investment; weakest phase.

## Activation & Retention Plan
| Friction / moment | Fix | Owner | Status |
|---|---|---|---|

## Discovery Cadence
Weekly touchpoint plan.
1# Artifact templates — grow-app
2 
3Skeletons this metaskill creates in the user's docs/ folder. Extend-only artifacts (CUSTOMER.md, EXPERIMENTS.md, DESIGN.md, OFFER.md, and the optional MARKETING.md / STRATEGY.md) are governed by the section headings named in each phase — read the existing file, add or update your sections, preserve everyone else's. The two skeletons below (METRICS.md, PRODUCT.md) are the files grow-app most often creates from scratch; copy them verbatim.
4 
5## Tracker: docs/GROW-APP-PLAN.md
6 
7Create this on first run (Intake). Phase rows are pre-filled; fill Status and Date as the journey advances.
8 
9```markdown
10# Grow an App Plan
11 
12## Context
13Intake answers, date started, project specifics.
14 
15## Phase Status
16| Phase | Skill | Status | Artifact | Date |
17|---|---|---|---|---|
18| 1. Habit loop | hooked-ux | pending | PRODUCT.md | |
19| 2. Activation | improve-retention | pending | PRODUCT.md | |
20| 3. Continuous discovery | continuous-discovery | pending | PRODUCT.md, CUSTOMER.md | |
21| 4. Lean UX experiments | lean-ux | pending | EXPERIMENTS.md | |
22| 5. Empowered team | inspired-product | pending | PRODUCT.md | |
23| 6. One metric that matters | lean-analytics | pending | METRICS.md | |
24| 7. Microinteractions | microinteractions | pending | DESIGN.md | |
25| 8. Intrinsic motivation | drive-motivation | pending | PRODUCT.md | |
26Statuses: pending · in-progress · awaiting-evidence · done · deferred: <reason> · skipped: <reason>
27 
28## Key Decisions
29| Date | Phase | Decision | Rationale |
30|---|---|---|---|
31 
32## Next Actions
33- [ ] action (owner, due)
34```
35 
36## docs/METRICS.md
37 
38Created in Phase 6 (lean-analytics). Creates: improve-business, grow-app.
39 
40```markdown
41# Metrics
42 
43## Stage & One Metric That Matters
44OMTM · counter-metric · why now.
45 
46## KPI Definitions
47| Metric | Definition | Actionable ratio? | Owner |
48|---|---|---|---|
49 
50## Baselines & Targets
51| Metric | Baseline (date) | Target | Line in the sand (miss response) |
52|---|---|---|---|
53 
54## Funnel
55| Stage | Conversion | Benchmark | Bottleneck? |
56|---|---|---|---|
57 
58## Cohort Notes
59```
60 
61## docs/PRODUCT.md
62 
63Extended across Phases 1, 2, 3, 5, and 8; create it here if the project has no PRODUCT.md yet. Creates: create-app, create-business. Extends: grow-app, improve-app.
64 
65```markdown
66# Product
67 
68## Vision
69One paragraph.
70 
71## MVP Definition
72Type, scope, what it deliberately excludes.
73 
74## Outcome Roadmap
75| Outcome / problem | Job served | Priority | Status |
76|---|---|---|---|
77 
78## Opportunity Solution Tree Notes
79 
80## Hook Model
81Trigger → Action → Variable reward → Investment; weakest phase.
82 
83## Activation & Retention Plan
84| Friction / moment | Fix | Owner | Status |
85|---|---|---|---|
86 
87## Discovery Cadence
88Weekly touchpoint plan.
89```
90 
View all files on GitHub →

Details

Updated
Sep 10, 2026
License
MIT
Stars on the repo
★ 2,235
Checked
Source
wondelai/skills ↗
Creator
wondelai · 319 listings
View creator

Similar skills

See all →

More from wondelai

SkillSoftware Design Philosophywondelai/skills · by wondelaiManage software complexity through deep modules, information hiding, and strategic programming. Use when the user mentions "module design", "API too complex", "shallow class", "complexity budget", "strategic vs tactical", "deep module", "information leakage", "pass-through method", "this code is over-engineered", or "simplify this design". Also trigger when reviewing an interface for simplicity, evaluating whether an abstraction is pulling its weight, deciding whether a comment is worth writing, or choosing between general-purpose and special-purpose approaches. Covers deep vs shallow modules, red flags for complexity, and comments as design documentation. For code quality, see clean-code. For architecture boundaries, see clean-architecture.★ 2.2k GitHub starsSkillActionable Metrics Guidewondelai/skills · by wondelaiMetrics are the language of validated learning. The wrong metrics create the illusion of progress while the startup drifts toward failure.…★ 2.2k GitHub starsSkillAdvertising Mediawondelai/skills · by wondelaiAdvertising media is the vehicle that carries your message to your target market. Choosing the right media is not about what is trendy — it…★ 2.2k GitHub starsSkillAffordance Designwondelai/skills · by wondelaiAn affordance is a relationship between an object and a person that determines how the object could possibly be used. A chair affords…★ 2.2k GitHub starsSkillLean UX in Agile Teamswondelai/skills · by wondelaiLean UX was designed to work inside Agile development teams, not alongside them. The central mechanism is dual-track agile, where a…★ 2.2k GitHub starsSkillAMP Framework Practitionerwondelai/skills · by wondelaiThis reference translates the AMP framework from theory into practice across six domains: product gamification, team management,…★ 2.2k GitHub stars