milestone_skill

Overview

This skill drives incremental implementation by advancing code in 100–200 LOC chunks, running tests after each change, and creating local milestone checkpoints when progress reaches the 800 LOC threshold without full completion. It focuses on measurable progress, continuous test validation, and clear checkpoint documents to resume work safely. The skill signals when the implementation is complete and ready for delivery.

How this skill works

The skill reads the implementation plan from the GitHub issue on first run or from the latest local milestone when resuming. It implements a single logical chunk (100–200 LOC), measures that chunk using git diff --stat, updates a cumulative LOC counter, runs the test suite, and parses test results. If cumulative LOC ≥ 800 and tests are not all passing it creates a local milestone report and stops; if all tests pass it signals completion.

When to use it

• Implement large features incrementally from an issue plan
• Resume interrupted implementation from a local milestone checkpoint
• Enforce test-driven progress with frequent validation
• Prevent runaway work by checkpointing when many LOC are added
• Coordinate multi-session work that needs a safe resumption point

Best practices

• Keep each implementation chunk to one logical unit (100–200 LOC) and break larger steps into substeps
• Run the full or relevant test subset after every chunk and capture output for parsing
• Accurately compute LOC from git diff --stat and maintain a cumulative count across sessions
• Create milestone documents locally (excluded from git) when threshold is reached and include work remaining and next-file estimates
• Stop immediately on critical test-run errors (syntax/import errors) and document the failures in the milestone

Example use cases

• Start implementing an issue plan from a GitHub issue and iterate until tests pass or a milestone is required
• Resume work after a break using the latest .milestones file and continue the LOC-counted loop
• Add feature tests and implementation in matching chunks, using test results to guide next steps
• Create a local checkpoint when blocked by integration failures so another developer can pick up where you left off