Individual skill

thrunt-milestone-summary

0upvotes

Generate a comprehensive project summary from milestone artifacts for team onboarding and review

thrunt-god/examples/brute-force-to-persistence/.github/skills/thrunt-milestone-summary/SKILL.md

Read pinned source

Source commit 6c1a49a70ff09453f4a95f47774b9cd5fabbc02f

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Not checked yet
Last checked: Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 41
Repository last updated: Jul 13, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

agent-skills Repository topic
agents Repository topic
ai-agent Repository topic
ai-agents Repository topic
claude-code Repository topic
detection-engineering Repository topic
threat-detection Repository topic
threat-hunting Repository topic
threat-intelligence Repository topic
thrunt Repository topic
engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 1,883 bytes

Read excerpt



<objective>
Generate a structured milestone summary for team onboarding and project review. Reads completed milestone artifacts (HUNTMAP, HYPOTHESES, CONTEXT, SUMMARY, VERIFICATION files) and produces a human-friendly overview of what was built, how, and why.

Purpose: Enable new team members to understand a completed project by reading one document and asking follow-up questions.
Output: MILESTONE_SUMMARY written to `.planning/reports/`, presented inline, optional interactive Q&A.
</objective>

<execution_context>
@.github/thrunt-god/workflows/milestone-summary.md
</execution_context>

<context>
**Project files:**