MCP App StoreMCP App Store
from my-cc-harness122
Create structured implementation plans for multi-step or architectural changes before coding — defines success criteria, trade-offs, and stepwise tasks.
This skill produces a detailed implementation plan before starting complex work. It guides the agent to define success criteria, list assumptions and constraints, compare alternate approaches, break the work into ordered steps (with estimated complexity and verification), and record risks and mitigations. The output is an actionable markdown checklist suitable for review and checkpoints.
Use this skill when a requested change involves 3+ steps, architecture decisions, multiple files, or ambiguous success criteria. Avoid for one-line edits or clear bug fixes. Triggers include requests to "plan", "design", "architecture", "how to implement", and Korean equivalents like "계획", "설계", "플랜".
Works with agents that can read and edit code and files (Codex/Claude-Code/CLI tooling). The skill expects access to repository files when used in a workplace automation flow.
Pure instruction skill (no scripts) that guides agents through structured planning before implementation — requirement analysis, code exploration, approach comparison, task breakdown, and risk identification. Written entirely in Korean, which limits its audience. The process it describes is sound but fairly generic; most capable agents already do this implicitly. No security concerns whatsoever since there are no scripts or executable content.
Language localization limits broad usefulness. The planning methodology is reasonable but not novel — it mirrors common software planning patterns. Would benefit from English translation and concrete examples to be more widely adoptable.
Harness Health Audit
Assess and score the overall health of a Claude Code harness across architecture, skills coverage, hooks, rules, MCP servers, eval pipelines, and team setup.
Code Evaluation Harness
Spawns an independent evaluator agent to score code outputs on functionality, code quality, originality, and usability/security, producing a structured EVAL_REP
SPEC-driven Development Interview
Conducts a structured, in-depth interview to produce a detailed SPEC.md requirements document for a feature or project.
Codex + Claude Code Review
Performs a dual-pass code review of the current branch using Codex (GPT) and Claude, producing structured findings and severity classifications.
Vercel React Best Practices
Practical performance and bundle-size guidelines for React and Next.js apps — prioritized rules and patterns to avoid common performance pitfalls.
Maestro Orchestrate
Orchestrates complex engineering workflows with enforced design and approval gates, child-agent delegation, and session state management.
Colorize (Strategic UI Color)
Introduce purposeful color into monochromatic or dull interfaces to improve hierarchy, meaning, and emotional warmth while preserving accessibility.
Execution Plan Splitter
Break large goals into 30/60/90-day execution plans with milestones, resource needs, and stop/go criteria for practical roadmaps.
BK-CI Design Patterns Guide
Practical guide to design patterns used in the BK-CI project (Kotlin/Spring). Covers factory, strategy, singleton, decorator, observer, template method, chain-o
Weekly Retro (Personal Corp)
Run a structured weekly retrospective: gather facts from repos and tools, interview the founder, and turn decisions into canonical files and issues.
Writing Implementation Plans
Generate detailed, engineer-ready implementation plans from design docs: file paths, step-by-step tasks, tests, and verification instructions.
Node.js Best Practices
Guidelines and decision-making for Node.js architecture, runtime, async patterns, security, validation, and testing to inform framework and system choices.
Build Unplanned Feature
Orchestrates ad-hoc feature development: requirement gathering, planning, implementation and validation across task-planning, implementation, and validation loo