Slash Command

/iterate

Conversationally edit the resume JSON — add roles, tweak bullets, reorder sections.

npx claudepluginhub danielrosehill/claude-code-plugins --plugin resume-typesetter

Details

Argument[variant]

Allowed Tools

ReadWriteEditBash

Prompt Preview

Iterate on the resume data file.

## Arguments

- `$1` — variant name (without `.json`). Default: base `resume.json`.

## Steps

1. **Load config** to find `dataRepo`. Fail gracefully if onboarding hasn't run.

2. **Resolve target file**: `<dataRepo>/data/variants/<$1>.json` or `<dataRepo>/data/resume.json`.

3. **Read the current file.** Summarise its structure briefly (e.g. "3 work entries, most recent: X"). Ask the user what they want to change.

4. **Apply edits.** Use the `Edit` tool for surgical changes to specific fields. For larger restructuring (e.g. reordering all work entries), r...

Command Content

Other plugins with /iterate

/iterate

Audits PI skill files like SKILL_META.md using self-rules: five dimensions + eighteen checks, logic chains, AgentSkills compliance, trigger purity, interaction completeness, style consistency, cross-references, scenario coverage; proposes precise iterative changes.

/iterate

Runs autonomous iteration loop: reads memory-bank/progress.md, selects next task via full/lite mode, executes with PM/Lead/Designer/Dev/QA roles or Dev/Verify/Commit, verifies, commits, updates progress, loops immediately to next.

12 tools

cc-best

/iterate

Initializes an autonomous iteration loop to repeat TASK until completion promise met or max iterations reached. Tracks progress in tasks/todo.md via git and files.

1 tool

ucai

Stats

Stars0

Forks0

Last CommitApr 20, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Iterate on the resume data file. ## Arguments - `$1` — variant name (without `.json`). Default: base `resume.json`. ## Steps 1. **Load config** to find `dataRepo`. Fail gracefully if onboarding hasn't run. 2. **Resolve target file**: `<dataRepo>/data/variants/<$1>.json` or `<dataRepo>/data/resume.json`. 3. **Read the current file.** Summarise its structure briefly (e.g. "3 work entries, most recent: X"). Ask the user what they want to change. 4. **Apply edits.** Use the `Edit` tool for surgical changes to specific fields. For larger restructuring (e.g. reordering all work entries), r...

Iterate on the resume data file.

Arguments

$1 — variant name (without .json). Default: base resume.json.

Steps

Load config to find dataRepo. Fail gracefully if onboarding hasn't run.
Resolve target file: <dataRepo>/data/variants/<$1>.json or <dataRepo>/data/resume.json.
Read the current file. Summarise its structure briefly (e.g. "3 work entries, most recent: X"). Ask the user what they want to change.
Apply edits. Use the Edit tool for surgical changes to specific fields. For larger restructuring (e.g. reordering all work entries), read, transform, and write back. Always keep the file as valid JSON Resume schema — never invent non-standard keys.
Validate that the file still parses as JSON (python3 -c "import json; json.load(open('...'))").
Offer next steps: render with /resume:render to see the effect, or /resume:version to snapshot.

Notes

Prefer minimal, targeted edits over full rewrites — the user should be able to see exactly what changed.
For tone/wording improvements on bullets, show the before and after before writing.
Don't auto-commit — let the user run /resume:version when they're ready.