Menu
Shared conventions for the solopreneur workflow. Preloaded into agents via the skills frontmatter field.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Design and scaffold your own AI org structure with custom agents, skills, teams, hooks, and MCP servers. Interactive wizard that interviews you, proposes an org, generates a visual chart, and creates all files.
Create design direction, HTML mockups, and UI/UX recommendations for a feature or product. Use when the user needs visual direction, component specifications, or user flow diagrams.
Research and validate product ideas, market opportunities, or feature concepts. Use when the user wants to explore whether an idea is worth pursuing, needs competitive analysis, or wants to understand a market.
Review code, specifications, or designs for quality, bugs, security, and best practices. Use when the user wants feedback on recent work, a pull request, or any artifact.
Execute a batch of backlog tickets in parallel. Use when the user wants to build multiple unblocked tickets simultaneously with integrated QA review.
Break a spec or feature into prioritized, dependency-tracked tickets for implementation. Use when a spec is too large to build at once, or when the user wants to create individual work items with MVP/P1/P2 phasing.
| name | conventions |
| user-invocable | false |
| description | Shared conventions for the solopreneur workflow. Preloaded into agents via the skills frontmatter field. |
These conventions are the single source of truth for shared formats across the solopreneur workflow.
Tickets are YAML-frontmatter markdown files in .solopreneur/backlog/{project}/:
---
id: MVP-001
title: Short descriptive title
priority: MVP | P1 | P2
type: eng | design | eng+design
status: pending | in-progress | built | tested | done
depends_on: []
blocks: []
design_ref: .solopreneur/designs/{dir}/{screen}.html
branch: ticket/{ID}
worktree: /path/to/worktree
---
## Description
What this ticket implements and why.
## Acceptance Criteria
- [ ] Criterion 1
- [ ] Criterion 2
## Technical Notes
Stack choices, approach, risks.
## Files
(Populated during build)
pending → in-progress (build starts)
in-progress → built (build completes)
built → tested (QA passes in review)
tested → done (merged to main in review)
Skills contain the operational instructions for the orchestrator. If the state machine changes, update these locations:
pending → in-progress: build/SKILL.md (line 43), sprint delegates to buildin-progress → built: build/SKILL.md (line 150), sprint/SKILL.md (line 99)built → tested: review/SKILL.md (line 51)tested → done: review/SKILL.md (lines 58, 99)When producing review findings, rate every issue:
Implementation plans use this structure:
# Plan: [Feature Name]
## Context
[What we're building and why. Reference source spec/design if applicable.]
**Branch**: `ticket/{ID}` (if ticket build)
## Step N: [Short description]
**Files**: `path/to/file.ext` (create|modify)
**Do**: [Clear, specific instructions for what to write]
**Acceptance**: [Concrete criteria to verify this step is done]