Skill

mdimplement

Execute implementation plan with testing and verification

Parent stars

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/md3step:mdimplement path/to/2_plan.md

User invocable

Model invocable

Inline context

Default effort

Argument hintpath/to/2_plan.md

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

**TERSE MODE:** Minimal output. Bullet points. Technical language.

25 lines · ~321 tokens

Stats

LanguageShell

Parent stars1

MaintenanceGood

Last CommitMay 21, 2026

Actions

Stats

Actions

Tags

TERSE MODE: Minimal output. Bullet points. Technical language.

IMMEDIATE EXIT if no argument:

If $ARGUMENTS is empty/missing: output "❌ Error: Path to 2_plan.md required. Usage: /mdimplement <path/to/2_plan.md>" and STOP immediately.

Read $ARGUMENTS - Abort if not found: "❌ Error: Plan file not found at $ARGUMENTS". Warn if Open Questions unresolved.
Check prerequisites
Execute each step: Read files, make changes (Edit/Write), run verification, document. If fail: fix/document/alert.
Run final tests
Write 3_changelog.md in same directory as $ARGUMENTS:
- # Implementation Changelog: [Topic] with date, Summary
- Per-step: Status (✓/⚠/✗), Files (path:line), Verify output
- Test Results, Known Issues
- at the top put a # Gothas section if issues arose with terse "- :\n - challenge: ... \n - solution: ..." format.
Compact the 3_changelog.md try making it ~50% of length.
Output: "✨ Implementation complete ✨. Created 3_changelog.md [X/Y steps, Z tests passed]"

NO git commits. Verify before proceeding. Changelog ultra-terse: facts, statuses, path:line refs only.