skill iter tune

AI Community

Skill notes

Key Design Principles

Iteration Loop: Phases 2-3-4 repeat until quality threshold, max iterations, or convergence Two-Tool Pipeline: Claude (write/execute) + Gemini (analyze/evaluate) = complementary perspectives Pure Orchestrator: SKILL.md coordinates only — execution detail lives in phase files Progressive Phase Loading: Phase docs read only when that phase executes Skill Versioning: Each iteration snapshots skill state before execution

Execution Flow

⚠️ COMPACT DIRECTIVE: Context compression MUST check TodoWrite phase status. The phase currently marked in_progress is the active execution phase — preserve its FULL content. Only compress phases marked completed or pending.

Phase 1: Setup (one-time)

Read and execute: Ref: phases/01-setup.md Parse skill paths, validate existence Create workspace at .workflow/.scratchpad/skill-iter-tune-{ts}/ Backup original skill files Initialize iteration-state.json

Phase 2: Execute Skill (per iteration)

Read and execute: Ref: phases/02-execute.md Snapshot skill → iteration-{N}/skill-snapshot/ Build execution prompt from skill content + test scenario Execute: ccw cli -p "..." --tool claude --mode write --cd "${iterDir}/artifacts" Collect artifacts

Phase 3: Evaluate Quality (per iteration)

Read and execute: Ref: phases/03-evaluate.md Build evaluation prompt with skill + artifacts + criteria + history Execute: ccw cli -p "..." --tool gemini --mode analysis Parse 5-dimension score (Clarity, Completeness, Correctness, Effectiveness, Efficiency) Write iteration-{N}-eval.md

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@catlog22 · no license declared
Token usage
Heavy
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Phase 1: Setup (one-time)

Read and execute: `Ref: phases/01-setup.md` Parse skill paths, validate existence Create workspace at `.workflow/.scratchpad/skill-iter-tune-{ts}/` Backup original skill files Initialize iteration-state.json

02
Phase 2: Execute Skill (per iteration)

Read and execute: `Ref: phases/02-execute.md` Snapshot skill → `iteration-{N}/skill-snapshot/` Build execution prompt from skill content + test scenario Execute: `ccw cli -p "..." --tool claude --mode write --cd "${iterDir}/artifacts"` Collect artifacts

03
Phase 3: Evaluate Quality (per iteration)

Read and execute: `Ref: phases/03-evaluate.md` Build evaluation prompt with skill + artifacts + criteria + history Execute: `ccw cli -p "..." --tool gemini --mode analysis` Parse 5-dimension score (Clarity, Completeness, Correctness, Effectiveness, Efficiency) Write `iteration-{N}-eval.md`

04
Phase 4: Apply Improvements (per iteration, skipped on termination)

Read and execute: `Ref: phases/04-improve.md` Read evaluation suggestions Launch general-purpose Agent to apply changes Write `iteration-{N}-changes.md` Update state

05
Phase 5: Final Report (one-time)

Read and execute: `Ref: phases/05-report.md` Generate comprehensive report with score progression table Write `final-report.md` Display summary to user Phase Reference Documents (read on-demand when phase executes):

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.