By mtrense
Multi-phase research workflow for building cited, audited knowledge bases — inquiry, investigation, consistency/coverage/quality/coherence audits, refinement, and glossary sync.
Per-topic coherence auditor for the research workflow. Given a single topic file path, assesses logical progression, transition smoothness, abstraction-level consistency, intro/setup adequacy, and heading-vs-content match. Returns a structured list of findings keyed to line numbers, with recommended AUDIT severities. Does NOT edit any files — the orchestrating `/research-audit-coherence` skill applies the AUDIT comments.
Web-verification worker for the four research-audit skills. Given a list of `<!-- CONFIDENCE: low -->` and `<!-- CONFIDENCE: medium -->` markers plus the surrounding claims, runs WebSearch + WebFetch to verify each one, and returns a structured per-marker decision (verified / failed / partial / contradiction-found) along with reference-update payloads. Does NOT edit any project files — the orchestrating audit skill does the actual edits.
Per-topic quality auditor for the research workflow. Given a single topic file path, assesses depth-vs-scale, sourcing adequacy, citation presence, reference verification, and example concreteness. Returns a structured list of findings keyed to line numbers, with recommended AUDIT severities. Does NOT edit any files — the orchestrating `/research-audit-quality` skill applies the AUDIT comments.
Web-research worker for the research workflow. Given a single RESEARCH directive (query, scale, sources, sources_detail, related), runs WebSearch + WebFetch loops to find and verify sources, then returns a structured report of vetted citations, verbatim quote snippets keyed to citation slugs, per-claim confidence assessments, contradictions between sources, and URL verification status. Does NOT write topic content — synthesis is the orchestrating skill's job. Read-only with respect to the project; touches the network only.
Per-topic glossary candidate extractor for the research workflow. Given one topic file, scans for explicitly defined terms, domain jargon, and key concepts, then returns a structured candidate list with definitions derived from how each term is used in the file. Does NOT edit any files — the orchestrating `/research-glossary-sync` skill merges candidates across topics and writes the glossary.
Add new chapter stubs to an existing topic directory in a research project. Use when a topic already exists as a directory and you want to introduce additional chapters. Argument: topic directory name (relative to research/content/).
Add a new topic (directory + chapter stubs) to an existing research project. Use when the project already exists and you want to introduce a new top-level topic area. Arguments: topic name (required), optional summary to seed scoping.
Audit research topics for narrative flow and coherence. Produces AUDIT directive comments for the refine phase. Arguments: optional topic path.
Audit research topics for cross-topic contradictions and inconsistent terminology. Produces AUDIT directive comments for the refine phase. Arguments: optional topic path.
Audit research topics for gaps relative to the research plan. Produces AUDIT directive comments for the refine phase. Arguments: optional topic path.
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 |
Four-phase milestone-driven build cycle: strategic planning, milestone breakdown, TDD task implementation, and milestone closing.
Bootstraps 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.
Cross-workflow utilities: /commit (the single commit point for all workflows), /pr, /audit-context, and /deckset.
npx claudepluginhub mtrense/skills --plugin researchComprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review
A growing collection of Claude-compatible academic workflow bundles. Covers scientific figures, manuscript writing and polishing, reviewer assessment, citation retrieval, data availability, paper reading, literature search, response letters, paper-to-PPTX conversion, and evidence-grounded Chinese invention patent drafting. Rules are organized as reusable skill folders with explicit workflows and quality checks.
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Tools to maintain and improve CLAUDE.md files - audit quality, capture session learnings, and keep project memory current.
Develop, test, build, and deploy Godot 4.x games with Claude Code. Includes GdUnit4 testing, web/desktop exports, CI/CD pipelines, and deployment to Vercel/GitHub Pages/itch.io.
Comprehensive PR review agents specializing in comments, tests, error handling, type design, code quality, and code simplification