architecture-principle…
Architecture principles for manifest-dev: how its maintainer wants skills, wrappers, references, state and the workflow…
Improve an existing artifact round after round toward a goal — a page, a prompt, a document, code whose speed matters, a simulation — keeping a change only when it measures better, until rounds bring no confirmed gain. Runs figure-out, define and do; quick by default, thorough
Claude Code
$ npx -y skills add doodledood/manifest-dev --skill hillclimb --agent claude-code
Codex
$ npx skills add doodledood/manifest-dev --skill hillclimb -a codex -y
Cursor
$ npx skills add doodledood/manifest-dev --skill hillclimb -a cursor -y
Gemini CLI
$ npx skills add doodledood/manifest-dev --skill hillclimb -a gemini-cli -y
GitHub Copilot
$ npx skills add doodledood/manifest-dev --skill hillclimb -a github-copilot -y
OpenCode
$ npx skills add doodledood/manifest-dev --skill hillclimb -a opencode -y
Windsurf
$ npx skills add doodledood/manifest-dev --skill hillclimb -a windsurf -y
name: hillclimb description: 'Improve an existing artifact round after round toward a goal — a page, a prompt, a document, code whose speed matters, a simulation — keeping a change only when it measures better, until rounds bring no confirmed gain. Runs figure-out, define and do; quick by default, thorough when asked or when the stakes call for it. Use when the user asks to hill-climb, optimize, keep improving or make something as good as it can be for its goal, or to continue an earlier climb.' argument-hint: '<target> [goal and measure] [--autonomous]' user-invocable: true
Hill-climb the target the arguments name toward the goal they state, in the requester's words, with any measure or results from real use they bring. With no target given or inferable, halt with usage.
This command holds no loop of its own: it is the same request made to figure-out, define and do, whose task files for climbs say what a climb owes. Tell each that this is a hill-climb on the target, and pass the request as given. A climb continuing an earlier one names that climb's Manifest or record, found through the execution logs that name this target or the record the requester points to.
then `define --autonomous`. Nobody is asked from start to end.
Do not set or print a continuation goal during understanding or definition, and tell figure-out that it runs chained under this command, which continues from its Read as a checkpoint: /do owns the completion backstop, and automatic continuation begins at execution.
When `define` reports the Manifest path, invoke `do` with that exact path in the same turn, unless the requester asked to stop at the plan. No path → stop and report. An attended climb asks at the end whether to push, unless the requester already said.
Hand your agent a task. Get back work you can trust. manifest-dev is a set of free, open-source skills for coding agents.
Architecture principles for manifest-dev: how its maintainer wants skills, wrappers, references, state and the workflow…
Ship a change to a file setup-project copies or emits into projects (ADR_FORMAT.md, NORTH_STAR_FORMAT.md, the verification…
Design principles for manifest-dev: how its maintainer wants the visual and interaction design guidance the plugin ships, and the…
Harden a manifest-dev task guidance file for one-shot quality — either /define''s quality-gate/Default set or figure-out''s probe…
Analyze Claude Code sessions to learn what went right/wrong and suggest high-confidence improvements to skills. Use when asked to…
The red-flag lists mirrored between figure-out''s and define''s task files, so a change to one side lands on the other. Use when…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.