Stats
Actions
Tags
From resume-typesetter
Conversationally edit the resume JSON — add roles, tweak bullets, reorder sections.
How this command is triggered — by the user, by Claude, or both
Slash command
/resume-typesetter:iterate [variant]This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
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.
$1 — variant name (without .json). Default: base resume.json.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.
/resume:version when they're ready.npx claudepluginhub danielrosehill/claude-code-plugins --plugin resume-typesetter/iterateUpdates any phase document (BRAINSTORM, DEFINE, DESIGN) when requirements or design changes, with version tracking and optional cascade to downstream documents.
/iterateAudits 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.
/iterateRuns 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.
/iterateInitializes 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.
/iterateDeprecated command for iterating on Jira PRs by ticket key (e.g., PROJ-123 --max_iterations 3). Use /jira:pr --iterate instead.