Business Improvement Templates

Artifact Templates — improve-business

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

Artifact Templates — improve-business cover

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

# Artifact Templates — improve-business

Skeletons this metaskill creates in the user's docs/ folder. Extend-only artifacts (CUSTOMER.md, OFFER.md, POSITIONING.md) are governed by the section headings named in each phase — do not restate their skeletons here; add under the exact headings the registry defines.

## docs/IMPROVE-BUSINESS-PLAN.md (tracker)

Create on first run with every phase pre-statused. Never shared with another journey.

```markdown
# Improve Business Plan

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

## Phase Status
| Phase | Skill | Status | Artifact | Date |
|---|---|---|---|---|
| 1 Diagnose the challenge | good-strategy-bad-strategy | pending | STRATEGY.md | |

Overview

Skeletons this metaskill creates in the user's docs/ folder. Extend-only artifacts (CUSTOMER.md, OFFER.md, POSITIONING.md) are governed by the section headings named in each phase — do not restate their skeletons here; add under the exact headings the registry defines.

Manual install (npx, ZIP)
Claude Codenpx skills add wondelai/skills --skill artifact-templates-improve-business -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.8 KB
Read artifact-templates.md here
wondelai/main1 file
artifact-templates.md
Show the full text113 lines

Artifact Templates — improve-business

Skeletons this metaskill creates in the user's docs/ folder. Extend-only artifacts (CUSTOMER.md, OFFER.md, POSITIONING.md) are governed by the section headings named in each phase — do not restate their skeletons here; add under the exact headings the registry defines.

docs/IMPROVE-BUSINESS-PLAN.md (tracker)

Create on first run with every phase pre-statused. Never shared with another journey.

# Improve Business Plan

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

## Phase Status
| Phase | Skill | Status | Artifact | Date |
|---|---|---|---|---|
| 1 Diagnose the challenge | good-strategy-bad-strategy | pending | STRATEGY.md | |
| 2 Install execution rhythm | traction-eos | pending | OPERATIONS.md | |
| 3 Manage for output | high-output-management | pending | OPERATIONS.md | |
| 4 Reshape teams | team-topologies | pending | OPERATIONS.md | |
| 5 Re-motivate the team | drive-motivation | pending | OPERATIONS.md | |
| 6 One metric that matters | lean-analytics | pending | METRICS.md | |
| 7 Protect margin | negotiation | pending | CUSTOMER.md | |
| 8 Reprice around value | monetizing-innovation | pending | OFFER.md | |
Statuses: pending · in-progress · awaiting-evidence · done · deferred: <reason> · skipped: <reason>

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

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

docs/STRATEGY.md (Phase 1 creates)

# Strategy

## Diagnosis
The single critical challenge.

## Guiding Policy

## Coherent Actions
| Action | Owner | Due | Status |
|---|---|---|---|

## No-List
What we explicitly will not do.

## Strategy Canvas & ERRC Grid
| Factor | Eliminate | Reduce | Raise | Create |
|---|---|---|---|---|

## Beachhead
Target segment, scoring rationale.

## Whole-Product Checklist
- [ ] gap (owner, priority)

docs/OPERATIONS.md (Phase 2 creates; Phases 3-5 extend)

# Operations

## Vision/Traction Summary
Core values · focus · 10-year/3-year/1-year picture.

## Rocks (this quarter)
| Rock | Owner | Binary done-condition | Status |
|---|---|---|---|

## Team Structure
Accountability chart / team topology; cognitive-load notes.

## Meeting Cadence
| Meeting | Rhythm | Agenda |
|---|---|---|

## Management Leverage
1:1 cadence, delegation decisions.

## Motivation (Autonomy / Mastery / Purpose)
| Lever | Finding | Fix |
|---|---|---|

docs/METRICS.md (Phase 6 creates)

# 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
1# Artifact Templates — improve-business
2 
3Skeletons this metaskill creates in the user's docs/ folder. Extend-only artifacts (CUSTOMER.md, OFFER.md, POSITIONING.md) are governed by the section headings named in each phase — do not restate their skeletons here; add under the exact headings the registry defines.
4 
5## docs/IMPROVE-BUSINESS-PLAN.md (tracker)
6 
7Create on first run with every phase pre-statused. Never shared with another journey.
8 
9```markdown
10# Improve Business Plan
11 
12## Context
13Intake answers, date started, project specifics.
14 
15## Phase Status
16| Phase | Skill | Status | Artifact | Date |
17|---|---|---|---|---|
18| 1 Diagnose the challenge | good-strategy-bad-strategy | pending | STRATEGY.md | |
19| 2 Install execution rhythm | traction-eos | pending | OPERATIONS.md | |
20| 3 Manage for output | high-output-management | pending | OPERATIONS.md | |
21| 4 Reshape teams | team-topologies | pending | OPERATIONS.md | |
22| 5 Re-motivate the team | drive-motivation | pending | OPERATIONS.md | |
23| 6 One metric that matters | lean-analytics | pending | METRICS.md | |
24| 7 Protect margin | negotiation | pending | CUSTOMER.md | |
25| 8 Reprice around value | monetizing-innovation | pending | OFFER.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/STRATEGY.md (Phase 1 creates)
37 
38```markdown
39# Strategy
40 
41## Diagnosis
42The single critical challenge.
43 
44## Guiding Policy
45 
46## Coherent Actions
47| Action | Owner | Due | Status |
48|---|---|---|---|
49 
50## No-List
51What we explicitly will not do.
52 
53## Strategy Canvas & ERRC Grid
54| Factor | Eliminate | Reduce | Raise | Create |
55|---|---|---|---|---|
56 
57## Beachhead
58Target segment, scoring rationale.
59 
60## Whole-Product Checklist
61- [ ] gap (owner, priority)
62```
63 
64## docs/OPERATIONS.md (Phase 2 creates; Phases 3-5 extend)
65 
66```markdown
67# Operations
68 
69## Vision/Traction Summary
70Core values · focus · 10-year/3-year/1-year picture.
71 
72## Rocks (this quarter)
73| Rock | Owner | Binary done-condition | Status |
74|---|---|---|---|
75 
76## Team Structure
77Accountability chart / team topology; cognitive-load notes.
78 
79## Meeting Cadence
80| Meeting | Rhythm | Agenda |
81|---|---|---|
82 
83## Management Leverage
841:1 cadence, delegation decisions.
85 
86## Motivation (Autonomy / Mastery / Purpose)
87| Lever | Finding | Fix |
88|---|---|---|
89```
90 
91## docs/METRICS.md (Phase 6 creates)
92 
93```markdown
94# Metrics
95 
96## Stage & One Metric That Matters
97OMTM · counter-metric · why now.
98 
99## KPI Definitions
100| Metric | Definition | Actionable ratio? | Owner |
101|---|---|---|---|
102 
103## Baselines & Targets
104| Metric | Baseline (date) | Target | Line in the sand (miss response) |
105|---|---|---|---|
106 
107## Funnel
108| Stage | Conversion | Benchmark | Bottleneck? |
109|---|---|---|---|
110 
111## Cohort Notes
112```
113 
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