By emingenc
Dual-track workflow plugin for Claude Code: Track 1 (surgical fixes) and Track 2 (spec-driven features). Enforces TDD, context budgets, PTC scripts, and micro-task decomposition via the MACHINE framework.
npx claudepluginhub emingenc/harness-engineering --plugin harness-engineeringAuto-execute Track 2 tasks with HIL-only pauses
Display task progress dashboard with dependency graph and metrics
Track 2 Phase 4: Execute one micro-task from tasks.json with TDD
Track 1: Apply a surgical fix to the codebase
Write a structured handoff document for context transfer between sessions
Scaffold a new Claude Code skill using the skill-factory
Track 2 Phase 2: Generate a design document with bi-directional prompting
Track 2 Phase 1: Research a topic using parallel sub-agents and PTC scripts
Track 2 Phase 3: Split annotated design.md into tasks.json
Show progress overview: tasks, sessions, and state
Run verification suite: structural checks, schema validation, and integrity
Execute one micro-task from tasks.json using TDD. Use when user says "execute", "run next task", "implement next", "continue execution", or runs /execute. This is the fourth phase of Track 2. Enforces TDD gate: failing tests FIRST, then implementation.
Generate design documents for Track 2 features. Use when user says "plan this", "design this feature", "create a plan", "write a design doc", or after research is complete and the user wants to move to planning. This is the second phase of Track 2.
Improve and enhance prompts for LLM interactions. Use when user says "improve this prompt", "make this prompt better", "enhance prompt", "review my prompt", or shares a prompt and asks for feedback.
Conduct codebase research using parallel sub-agents and PTC scripts. Use when user says "research", "investigate", "explore", "understand how", "find out about", "analyze the codebase", or before planning a feature. This is the first phase of Track 2.
Create new Claude Code skills from scratch. Use when the user says "new skill", "create a skill", "make a skill for X", "turn this into a skill", "automate this pattern", or "scaffold a skill".
Apply surgical fixes to codebases. Use when the user says "fix this bug", "quick fix", "small change", "patch this", "update this config", or describes a problem that can be solved by modifying 1-3 files. Do NOT use for features requiring design docs or multi-step planning.
Split an annotated design document into micro-tasks in tasks.json. Use when user says "split", "break down", "create tasks", "generate tasks", or after a design.md has been annotated and the user runs /split. This is the third phase of Track 2.
Battle-tested Claude Code plugin for engineering teams — 48 agents, 184 skills, 79 legacy command shims, production-ready hooks, and selective install workflows evolved through continuous real-world use
Complete collection of battle-tested Claude Code configs from an Anthropic hackathon winner - agents, skills, hooks, rules, and legacy command shims evolved over 10+ months of intensive daily use
Complete collection of battle-tested Claude Code configs agents, skills, hooks, rules, and legacy command shims evolved over 10+ months of intensive daily use
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Works with Claude Code, Kiro, Clawd CLI, Gemini CLI, Cursor, Continue, Hermes, and 17+ AI coding assistants. Now with Arabic, German, Spanish, and Chinese (Simplified & Traditional) support.
AI-supervised issue tracker for coding workflows. Manage tasks, discover work, and maintain context with simple CLI commands.