By mtrense
Four-phase milestone-driven build cycle: strategic planning, milestone breakdown, TDD task implementation, and milestone closing.
Reconnaissance worker for `/milestone-breakdown`. Given a milestone description and a repo root, scouts the codebase for everything the orchestrator needs to decompose the milestone into tasks: relevant files, code conventions, test posture, data models / schemas, framework usage, and risks. Returns a structured report. Does NOT propose tasks — synthesis is the orchestrator's job. Read-only.
Implementation-cycle worker. Runs `task-implementation` followed by `commit` on a single PLAN.md task and exits with a parser-friendly report block. Used by `/implementation-cycle` to keep the orchestrator session lean — the full implementation transcript (file reads, test runs, iteration on errors) lives in this subagent and is discarded on return.
Drive PLAN.md to completion by running task-implementation + commit in a fresh subagent per task, sequentially.
Break down the next open milestone from ROADMAP.md into small, actionable, independently testable tasks in PLAN.md. Trigger whenever the user says "break down", "plan tasks", "create tasks", "task breakdown", "decompose milestone", "phase 2", "let's break this down", references PLAN.md in a planning context, or asks to prepare for implementation. Also trigger when the user has just finished strategic planning and wants to move to the next phase. This skill reads the codebase and docs to produce implementation-aware tasks with architectural hints, test cases, and file associations.
Close out a completed milestone by documenting results, noting discrepancies, adding manual testing/demo steps, and preparing PLAN.md for the next cycle. Trigger whenever the user says "close milestone", "milestone done", "wrap up", "close it out", "phase 4", "finish the milestone", "we're done", or when all tasks in PLAN.md are marked complete and the user wants to finalize. Also trigger when the user asks to document what was built, write demo steps, or prepare for the next planning cycle.
Facilitate project inception for new software projects by discovering the project's vision, goals, and planned feature set through Socratic dialogue, then producing a concise README.md and a CLAUDE.md with project-specific instructions for AI-assisted development. This skill precedes the four-phase milestone-driven workflow — use it once at the very beginning to establish the project's identity before strategic planning begins.
Facilitate strategic planning for AI-native software projects by adding new milestones to ROADMAP.md through Socratic dialogue. Trigger whenever the user mentions adding a milestone, starting a new feature, planning a new capability, discussing project direction, or says things like "let's plan", "new milestone", "next feature", "I want to build", "add to the roadmap", or references ROADMAP.md. Also trigger when the user starts describing a high-level goal or user-facing feature they want to pursue next. This skill is the entry point of a four-phase milestone-driven workflow — use it for the strategic/planning phase, not for breaking down tasks or implementing code.
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A collection of prompt-based skills for Claude Code that add structured workflows for software engineering and research.
Skills are markdown files with YAML frontmatter that Claude loads as playbooks. Each skill provides a /slash-command — you invoke it, and Claude follows the skill's instructions to guide you through a specific workflow phase.
This repo can be installed two ways: as a Claude Code plugin marketplace (recommended for end users) or via the legacy symlink installer (recommended for developing/iterating on the skills themselves).
The repo root carries a .claude-plugin/marketplace.json catalog (mtrense-skills). Each workflow family is exposed as a separately-installable plugin with its own <workflow>/.claude-plugin/plugin.json manifest.
/plugin marketplace add mtrense/skills
/plugin install milestone-driven@mtrense-skills
/plugin install research@mtrense-skills
/plugin install codebase-survey@mtrense-skills
/plugin install common@mtrense-skills
Updates: /plugin marketplace update. No version field is pinned, so each commit on main is treated as a new version.
# Install every workflow globally (~/.claude/skills/ + ~/.claude/agents/)
./install.sh all
# Install just one workflow globally
./install.sh milestone-driven
# Install one workflow into a specific project
./install.sh research /path/to/project
The first argument is the workflow name (codebase-survey, common, milestone-driven, research) or all. The optional second argument is the install target (defaults to $HOME). The installer creates symlinks, so skills stay up to date as you pull changes.
A phased cycle for building software, from idea through implementation to closeout. Each phase produces a specific artifact that feeds into the next.
| Phase | Command | What it does | Produces |
|---|---|---|---|
| 0 | /project-inception | Socratic dialogue to discover project vision and goals | README.md |
| 1 | /strategic-planning | Sharpen ideas into well-defined, testable milestones | ROADMAP.md entries |
| 2 | /milestone-breakdown | Decompose a milestone into ordered, independently testable tasks | PLAN.md |
| 3 | /task-implementation | Implement one task using strict TDD (tests first, then code) | Passing code + tests |
| 3 | /implementation-cycle | Run task-implementation + commit in fresh subagents per task to keep the main session clean | Passing code + commits |
| 4 | /milestone-closing | Verify success criteria, document results, reset for next cycle | Updated ROADMAP.md |
| - | /commit | Craft a conventional commit from staged/unstaged changes | Git commit |
Typical flow: inception (once) -> planning -> breakdown -> implementation (repeat per task) -> closing -> back to planning.
The milestone-driven workflow uses two bundled subagents: milestone-scout (delegated codebase reconnaissance for milestone-breakdown) and task-worker (per-task task-implementation + commit worker for implementation-cycle). Both live in milestone-driven/agents/ and are installed alongside the workflow's skills.
A multi-phase system for building structured knowledge bases with source verification and quality auditing.
| Phase | Command | What it does |
|---|---|---|
| 1 | /research-inception | Create project structure: INDEX.md, DECISIONS.md, glossary, topic stubs |
| - | /research-add-topic | Add a new topic (directory + chapter stubs) to an existing project |
| - | /research-add-chapter | Add new chapter stubs to an existing topic directory |
| 2 | /research-inquiry | Add section outlines with RESEARCH directives to a chapter |
| 3 | /research-investigation | Write content for one section; delegates the search-fetch-verify loop to the source-investigator subagent |
| 4 | /research-audit-consistency | Check cross-topic contradictions; insert AUDIT directives |
| 4 | /research-audit-coverage | Check gaps relative to the research plan; insert AUDIT directives |
| 4 | /research-audit-quality | Check depth and sourcing adequacy; insert AUDIT directives. Fans out per-topic analysis to quality-auditor in parallel |
| 4 | /research-audit-coherence | Check narrative flow; insert AUDIT directives. Fans out per-topic analysis to coherence-auditor in parallel |
| 5 | /research-refine | Resolve audit findings (correct, expand, condense, restructure) |
| 6 | /research-restructure | Structural changes: split, merge, promote, or demote topics |
| 7 | /research-glossary-sync | Reconcile glossary against current topic content. Fans out per-topic candidate extraction to term-extractor in parallel |
npx claudepluginhub mtrense/skills --plugin milestone-drivenBootstraps and maintains an AI-consumable map of an existing codebase: top-level + per-module CODEBASE.md, architecture assessment, and derived CLAUDE.md/AGENTS.md rules.
Multi-phase research workflow for building cited, audited knowledge bases — inquiry, investigation, consistency/coverage/quality/coherence audits, refinement, and glossary sync.
Cross-workflow utilities: /commit (the single commit point for all workflows), /pr, /audit-context, and /deckset.
Harness-native ECC operator layer - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses
Superpowers Plus core skills library for Claude Code: planning, execution routing, TDD, debugging, and collaboration workflows
Claude harness - A harness for solo developers (Vibecoders) to handle full-cycle contract development.
Persistent file-based planning for AI coding agents. Crash-proof markdown plans (task_plan.md, findings.md, progress.md) that survive context loss and /clear, with an opt-in completion gate and multi-agent shared state. Manus-style. Works with Claude Code, Codex CLI, Cursor, Kiro, OpenCode and 60+ agents via the SKILL.md standard. Includes Arabic, German, Spanish, and Chinese (Simplified and Traditional).
v9.44.1 — Patch release for Gemini environment/version detection and qwen auth gating. Run /octo:setup.
AI-powered development tools for code review, research, design, and workflow automation.