I’ve been using Claude Code for a while and kept running into the same problem: large tasks lose context. Requirements get forgotten, constraints get skipped, and you end up babysitting the conversation.
So I built
maistro — a CLI
that decomposes your goal into sequential tasks, executes them one at a time via Claude Code subprocess, validates results, and auto-commits. It works. I’ve used it for multi-hour autonomous runs, building entire apps from a single prompt.
But it comes with baggage: it needs --dangerously-skip-permissions, runs in a separate terminal, manages its own subprocess lifecycle. All reasonable for a CLI — but it’s a lot of machinery for what’s essentially breaking this into steps and keep context clean.
Then I realized Claude Code already has subagents. I could do the same thing as a skill. So I rebuilt it:
/maistro Build a REST API with auth, roles, and CRUD operations
/maistro <goal> │ ├─ Architect (discovery questions + task planning) │ └─ Interactive → writes .maistro/state.json │ └─ For each task: ├─ Developer (implements code, tests, simplifies) └─ QA (validates using the acceptance criteria) └─ PASS → commit, next task └─ FAIL → pass to Developer, skip, or fail
Easy to start, and now you have options not to allow all the permissions, although I still will do that for my session 🤔
The
maistro-skill
package is here. Easy to try:
npx maistro-skill install
Happy prompting, and do get some sleep!
submitted by
/u/dreamteammobile
Originally posted by u/dreamteammobile on r/ClaudeCode