setup-minimalship
Skill0 starsChanged 24 days agoMITView on GitHub
Configure a repository for the MinimalShip product-development workflow without imposing an issue tracker or hosted service.
In this repository29 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- minimalshipSkill
- ask-minimalshipSkill
- codebase-designSkill
- code-reviewSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- grill-with-docsSkill
- implementSkill
- implement-specSkill
- improve-codebase-architectureSkill
- prototypeSkill
- prSkill
- researchSkill
- retroSkill
- tddSkill
- to-specSkill
- to-ticketsSkill
- triageSkill
- wayfinderSkill
- wizardSkill
- grillingSkill
- grill-meSkill
- handoffSkill
- teachSkill
- to-questionnaireSkill
- wait-whatSkill
- writing-for-agentsSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Run once before using the larger flow in a new repository.
- Very specific: line 17
Keep docs/, analysis/, and .local/ local-only in this repository.
- Very specific: line 19
Do not invent labels, ticket infrastructure, a hosted service, STATUS.md, or another duplicate tracker just because another repository uses …
≈ “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
Set Up MinimalShip
Run once before using the larger flow in a new repository.
- Inspect existing
AGENTS.md,CLAUDE.md,README.md, tests, and package scripts. - Preserve existing conventions unless they conflict with truthful acceptance or safety.
- Confirm the product vocabulary and add only terms that affect code or decisions.
- Choose the work records:
FEATURES.mdfor the product inventory when feature tracking is needed, and rootRUN.mdfor the current cycle. Reuse an existing tracker only when the repository already has one and document the adapter. - Record the test, typecheck, build, start, and smoke commands that actually exist.
- Record whether Pi, Herdr, worktrees, network calls, installs, cloud dashboards, or deployment are allowed. These are execution boundaries, not reasons to require unrelated personal-preference answers.
- Keep
docs/,analysis/, and.local/local-only in this repository.
Do not invent labels, ticket infrastructure, a hosted service, STATUS.md, or another duplicate tracker just because another repository uses them.
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.