donny-milestone-summary

النجوم٨

التفرعات٠

آخر تحديث٣٠ يونيو ٢٠٢٦ في ٠٥:٣٥

Generate a human-readable milestone summary from the planning artifacts (ROADMAP, REQUIREMENTS, per-phase CONTEXT/SUMMARY/VERIFICATION) covering architecture, phases, key decisions, requirements, and tech debt. Use when someone needs to understand a finished or in-progress milestone from one document, for team onboarding or review.

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

المصدر

D0NMEGA

D0NMEGA/donnyclaude

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

مطوّرو البرمجياتمهن الحاسوب والرياضيات·SOC 15-1252

SKILL.md

readonly

name	donny-milestone-summary
description	Generate a human-readable milestone summary from the planning artifacts (ROADMAP, REQUIREMENTS, per-phase CONTEXT/SUMMARY/VERIFICATION) covering architecture, phases, key decisions, requirements, and tech debt. Use when someone needs to understand a finished or in-progress milestone from one document, for team onboarding or review.
argument-hint	[version]
allowed-tools	["Read","Write","Bash","Grep","Glob"]

Generate a structured milestone summary for team onboarding and project review. Reads completed milestone artifacts (ROADMAP, REQUIREMENTS, 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.

<execution_context> @~/.claude/donny/workflows/milestone-summary.md </execution_context>

**Project files:** - `.planning/ROADMAP.md` - `.planning/PROJECT.md` - `.planning/STATE.md` - `.planning/RETROSPECTIVE.md` - `.planning/milestones/v{version}-ROADMAP.md` (if archived) - `.planning/milestones/v{version}-REQUIREMENTS.md` (if archived) - `.planning/phases/*-*/` (SUMMARY.md, VERIFICATION.md, CONTEXT.md, RESEARCH.md)

User input:

Version: $ARGUMENTS (optional - defaults to current/latest milestone)

Read and execute the milestone-summary workflow from @~/.claude/donny/workflows/milestone-summary.md end-to-end.

<success_criteria>

Milestone version resolved (from args, STATE.md, or archive scan)
All available artifacts read (ROADMAP, REQUIREMENTS, CONTEXT, SUMMARY, VERIFICATION, RESEARCH, RETROSPECTIVE)
Summary document written to .planning/reports/MILESTONE_SUMMARY-v{version}.md
All 7 sections generated (Overview, Architecture, Phases, Decisions, Requirements, Tech Debt, Getting Started)
Summary presented inline to user
Interactive Q&A offered
STATE.md updated </success_criteria>

المزيد من هذا المستودع

نفس المستودع

continuous-learning-v2

D0NMEGA/donnyclaude

Instinct-based learning system that observes sessions via hooks, creates atomic instincts with confidence scoring, and evolves them into skills/commands/agents. v2.1 adds project-scoped instincts to prevent cross-project contamination.

2026-07-068

donny-add-backlog

D0NMEGA/donnyclaude

Adds an idea to the backlog parking lot using 999.x numbering, kept outside the active phase sequence so it accumulates context without being scheduled. Use when an idea is worth keeping but not ready to plan into the current milestone.

2026-06-308

donny-add-tests

D0NMEGA/donnyclaude

Generate unit and E2E tests for a completed phase, using its SUMMARY, CONTEXT, and VERIFICATION artifacts as the spec and gating unit tests on a mutation check. Use when a finished phase needs test coverage; requires the phase number and an existing SUMMARY.md.

2026-06-308

donny-analyze-dependencies

D0NMEGA/donnyclaude

Analyze the current milestone's phase dependency graph (file overlap, semantic and data-flow links) and suggest Depends on entries for ROADMAP.md. Use before parallel phase execution to prevent merge conflicts from unordered phases.

2026-06-308

donny-audit-milestone

D0NMEGA/donnyclaude

Audit a milestone against its definition of done before archiving: aggregate per-phase VERIFICATION results, cross-check requirements coverage from three sources, spawn an integration checker for cross-phase wiring, and emit a structured audit report. Use when wrapping up a milestone, before /donny-complete-milestone, to confirm nothing was missed.

2026-06-308

donny-audit-phase

D0NMEGA/donnyclaude

Retroactively audits a completed phase for security (threat mitigations from the PLAN.md threat model are implemented) and validation (Nyquist test coverage of the phase's requirements). Use after a phase is executed to confirm threats are closed and requirements are tested; runs both audits by default. --security or --validate narrows to one. Open threats block phase advancement.

2026-06-308

name	donny-milestone-summary
description	Generate a human-readable milestone summary from the planning artifacts (ROADMAP, REQUIREMENTS, per-phase CONTEXT/SUMMARY/VERIFICATION) covering architecture, phases, key decisions, requirements, and tech debt. Use when someone needs to understand a finished or in-progress milestone from one document, for team onboarding or review.
argument-hint	[version]
allowed-tools	["Read","Write","Bash","Grep","Glob"]

<execution_context> @~/.claude/donny/workflows/milestone-summary.md </execution_context>

User input:

Version: $ARGUMENTS (optional - defaults to current/latest milestone)

Read and execute the milestone-summary workflow from @~/.claude/donny/workflows/milestone-summary.md end-to-end.

<success_criteria>

Milestone version resolved (from args, STATE.md, or archive scan)
All available artifacts read (ROADMAP, REQUIREMENTS, CONTEXT, SUMMARY, VERIFICATION, RESEARCH, RETROSPECTIVE)
Summary document written to .planning/reports/MILESTONE_SUMMARY-v{version}.md
All 7 sections generated (Overview, Architecture, Phases, Decisions, Requirements, Tech Debt, Getting Started)
Summary presented inline to user
Interactive Q&A offered
STATE.md updated </success_criteria>