project-genesis
Skill12 starsChanged 47 days agoMITView on GitHub
Drive the full 5-phase Project Genesis Wizard, from raw idea to first coding sprint. Use when starting a new project from the AI Dev Operating System, when the user runs /project-start, or when they say "vamos começar um projeto novo", "tenho uma ideia de SaaS", "quero criar um app", "por onde eu começo?". Enforces the prototype-before-spec ordering (Phase 3 before Phase 4) and refuses to write code before Phase 5.
In this repository28 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- business-plan-impact-reviewSkill
- codemapSkill
- cost-watchdogSkill
- daily-standupSkill
- decision-logSkill
- deploy-vercel-supabaseSkill
- feature-scaffoldSkill
- first-100-usersSkill
- grow-sustainablySkill
- multi-ai-reviewSkill
- os-self-testSkill
- pitchSkill
- plain-portuguese-explainerSkill
- privacy-auditSkill
- processizeSkill
- product-briefSkill
- prototype-labSkill
- registry-pickSkill
- release-checkSkill
- research-wavesSkill
- rollback-safeSkill
- secrets-disciplineSkill
- secrets-scanSkill
- sprint-managementSkill
- sprint-roadmapSkill
- usage-monitorSkill
- verify-build-worksSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill when starting a new project from the AI Dev Operating System.
- Very specific: line 10
Follow WIZARD.md exactly. It runs in 5 phases, and none may be skipped:
- Distinctive: line 24
Do not write the Product Brief and then prototype against it: a spec written against a clickable prototype names the gaps that a spec …
- Distinctive: line 26
If the prototype seems to need the Product Brief, what it actually needs is missing from BP v0.0.2.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Project Genesis Skill
Use this skill when starting a new project from the AI Dev Operating System.
Follow WIZARD.md exactly. It runs in 5 phases, and none may be skipped:
| Phase | Must include |
| 1 — Largada | repository comprehension, detach from OS-origin, friendly opening |
| 2 — Ideação | raw ideation, ten questions, research plan approval, three research/review waves, BP v0.0.1, human review, BP v0.0.2 |
| 3 — Protótipo | design pack pick, Prototype Lab (3 directions), direction approved, DESIGN-DIRECTION.md written |
| 4 — Documentação | Product Brief, Technical Plan, stack pack pick, sprint roadmap |
| 5 — Chegada | Sprint 0 / Sprint 1 |
The one ordering mistake to avoid
Phase 3 comes before Phase 4. Prototype first, then reverse-engineer the Product Brief and Technical Plan from the direction the user approves.
Do not write the Product Brief and then prototype against it: a spec written against a clickable prototype names the gaps that a spec written against a paragraph quietly invents.
If the prototype seems to need the Product Brief, what it actually needs is missing from BP v0.0.2. Go back and add it there.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.