backbay-labs/thrunt-god/thrunt-complete-milestone
Claude Code and agent skill by backbay-labs/thrunt-god
- community
Checking that the SKILL.md file is still in the repository.
Archive completed milestone and prepare for next version
Install
npx vskill@latest install backbay-labs/thrunt-god/thrunt-complete-milestoneSKILL.md
The same SKILL.md was published earlier as backbay-labs/thrunt-god/thrunt-complete-milestone.
<objective> Mark milestone {{version}} complete, archive to milestones/, and update HUNTMAP.md and HYPOTHESES.md.
Purpose: Create historical record of published version, archive milestone artifacts (huntmap + requirements), and prepare for next milestone. Output: Milestone archived (huntmap + requirements), MISSION.md evolved, git tagged. </objective>
<execution_context> Load these files NOW (before proceeding):
- @.github/thrunt-god/workflows/complete-milestone.md (main workflow)
- @.github/thrunt-god/templates/milestone-archive.md (archive template)
</execution_context>
<context> Project files:
.planning/HUNTMAP.md.planning/HYPOTHESES.md.planning/STATE.md.planning/MISSION.md
User input:
- Version: {{version}} (e.g., "1.0", "1.1", "2.0")
</context>
<process>
Follow complete-milestone.md workflow:
- Check for audit:
- Look for
.planning/v{{version}}-MILESTONE-AUDIT.md - If missing or stale: recommend
/thrunt-audit-milestonefirst - If audit status is
gaps_found: recommend/thrunt-plan-milestone-gapsfirst - If audit status is
passed: proceed to step 1
```markdown ## Pre-flight Check
{If no v{{version}}-MILESTONE-AUDIT.md:} ⚠ No milestone audit found. Run /thrunt-audit-milestone first to verify requirements coverage, cross-phase integration, and E2E flows.
{If audit has gaps:} ⚠ Milestone audit found gaps. Run /thrunt-plan-milestone-gaps to create phases that close the gaps, or proceed anyway to accept as tech debt.
{If audit passed:} ✓ Milestone audit passed. Proceeding with completion. ```
- Verify readiness:
- Check all phases in milestone have completed plans (SUMMARY.md exists)
- Present milestone scope and stats
- Wait for confirmation
- Gather stats:
- Count phases, plans, tasks
- Calculate git range, file changes, LOC
- Extract timeline from git log
- Present summary, confirm
- Extract accomplishments:
- Read all phase SUMMARY.md files in milestone range
- Extract 4-6 key accomplishments
- Present for approval
- Archive milestone:
- Create
.planning/milestones/v{{version}}-HUNTMAP.md - Extract full phase details from HUNTMAP.md
- Fill milestone-archive.md template
- Update HUNTMAP.md to one-line summary with link
- Archive requirements:
- Create
.planning/milestones/v{{version}}-HYPOTHESES.md - Mark all v1 requirements as complete (checkboxes checked)
- Note requirement outcomes (validated, adjusted, dropped)
- Delete
.planning/HYPOTHESES.md(fresh one created for next milestone)
- Update MISSION.md:
- Add "Current State" section with published version
- Add "Next Milestone Goals" section
- Archive previous content in
<details>(if v1.1+)
- Commit and tag:
- Stage: MILESTONES.md, MISSION.md, HUNTMAP.md, STATE.md, archive files
- Commit:
chore: archive v{{version}} milestone - Tag:
git tag -a v{{version}} -m "[milestone summary]" - Ask about pushing tag
- Offer next steps:
/hunt-new-program— start next milestone (questioning → research → requirements → huntmap)
</process>
<success_criteria>
- Milestone archived to
.planning/milestones/v{{version}}-HUNTMAP.md - Hypotheses archived to
.planning/milestones/v{{version}}-HYPOTHESES.md .planning/HYPOTHESES.mddeleted (fresh for next milestone)- HUNTMAP.md collapsed to one-line entry
- MISSION.md updated with current state
- Git tag v{{version}} created
- Commit successful
- User knows next steps (including need for fresh requirements)
</success_criteria>
<critical_rules>
- Load workflow first: Read complete-milestone.md before executing
- Verify completion: All phases must have SUMMARY.md files
- User confirmation: Wait for approval at verification gates
- Archive before deleting: Always create archive files before updating/deleting originals
- One-line summary: Collapsed milestone in HUNTMAP.md should be single line with link
- Context efficiency: Archive keeps HUNTMAP.md and HYPOTHESES.md constant size per milestone
- Fresh requirements: Next milestone starts with
/hunt-new-programwhich includes requirements definition
</critical_rules>
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewNot runA model review is scheduled for the next rescan.
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingthrunt-god/examples/brute-force-to-persistence/.github/skills/thrunt-complete-milestone/SKILL.md
Popularity
- Repository stars
- 30
- Repository forks
- 5
- Repository npm downloads, 7 days
- 15
- 7-day trend score
- 33
Stars and forks are for the whole GitHub repository, not this skill alone. Downloads are for the repository's npm package. Refreshed 30 Apr 2026, 6 months ago.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/backbay-labs/thrunt-god/thrunt-complete-milestone)