The skills, agents and instructions I use as a professional Software Engineer. It's called Craft, and it's a plugin you can install.
View the Craft source on GitHub juanwmedia/craft$claude plugin install craft --marketplace juanwmedia/craft
You decide what the agent cannot infer: the domain, the architecture, the structure of what gets built.
Code is cheap once the uncertainty is gone. The decisions are written down and the agent builds on its own.
Every step is reviewed in a fresh context: the documents against the code before you see them, the code against the documents once it is built.
You decide what the agent cannot infer. After that, the loop runs on its own and every step is reviewed in a fresh context. Click the right or left side of the stage, or use the arrow keys.
An idea. You and Claude Code, nothing decided yet.
The loop starts with what the agent cannot infer: the domain, the architecture, the structure.
You: What we build and why. Agent: It interviews you until nothing blocking is left open; anything the code can answer, it looks up in the code.
You: That the slices are the right ones. Agent: It splits the work into slices that never touch the same file, each with its own check.
You: Nothing: your time in the loop ends here. Agent: It builds the slices in parallel, one agent per slice, passes every check and reviews the whole change.
You: Which proof counts. Agent: It tests the build live, end to end and in a browser when it applies, and records the evidence.
You: One yes. Agent: It reconciles the documentation with what was built, and then commits, pushes and opens a pull request.
You: Saying you're lost. Agent: It repeats the last answer until it lands, without moving the work forward.
You: Whether it works without you. Agent: Every question a phase would ask you goes to act-as-me, and detached.md keeps them for the morning.
You: Which piece of work to pick up. Agent: It says where each open piece of work stands, where it came from and what the next step is.
You: Showing it or hiding it. Agent: It shows the line above the prompt with the work, the phase, the slices and the agent running now.
You: Nothing. Implement launches it, one per slice. Agent: It builds its slice in a fresh context, changes only the files the slice lists, passes its check and reports.
You: Nothing. Shape, plan and close launch it. Agent: It audits a document in a fresh context and returns every claim the code does not back, with file and line. The evaluator-optimizer pattern: the draft is fixed and audited again.
You: Nothing. Implement launches it. Agent: It tries to refute the change against the documents and the repo's conventions, and returns confirmed, refuted or uncertain, with evidence.
You: Whether you let it answer for you. Agent: In detached mode it answers what a phase would ask you, as a pragmatic senior would: it checks the code first, answers with the why, or says it cannot decide.
The craft bar leaves this plugin and becomes craft-bar, installed from the same marketplace with /plugin install craft-bar@craft. The Claude plugin directory accepts mods only from Verified organizations, so craft ships no mod and the directory can list it. Updating craft alone removes the bar until craft-bar is installed; /craft:bar is now /craft-bar:bar.
detached for a phase the model starts with the Skill tool, the same as for one you type. Before, a phase started that way (a routine asking in words, a session moving on to the next phase) showed only craft./craft:detached answers one line, whether the mode is on or off in this repository, without the line about routines.Detached mode: craft carries a piece of work with nobody at the keyboard.
/craft:detached on turns it on and /craft:detached off ends it. A routine starts with /craft:detached on as its first message, or asks for the mode in words, since both /craft:detached and /craft:bar can now be called by the model.craft:act-as-me, which runs on Fable 5.1 in a fresh context and answers as an extremely pragmatic senior software engineer who takes nothing for granted. It checks the code first, answers with one option, given or its own, and why, and says Cannot decide with what is missing instead of inventing. When it cannot decide, or does not start, the phase stops and names the question.craft.detached in the repository's local git config: per repository, outside the tree, never committed.detached.md in the work's folder with its phase, the question, the answer and why, in order. It is the file to read in the morning, next to the pull request.craft:act-as-me says yes. The yes is logged in detached.md before the commit, so the commit carries it, and close says who gave it. You review the pull request.detached after the phase while the mode is on, and ends with an x that hides it, the same as /craft:bar off.AskUserQuestion call, craft:act-as-me started for the questions, the entry in detached.md.references/ask.md says, instead of naming the human or AskUserQuestion itself.