implement-plan-micro
Implement technical plans from thoughts/shared/plans with verification
Install
mkdir -p .claude/skills/implement-plan-micro && curl -L -o skill.zip "https://mcp.directory/api/skills/download/1120" && unzip -o skill.zip -d .claude/skills/implement-plan-micro && rm skill.zipInstalls to .claude/skills/implement-plan-micro
About this skill
Formal Specification
Multimodal Logic Integration
Five modal logics via fusion with bridge principles:
- JL: Justification Logic - evidence-backed claims
- IEL: Inferential Erotetic Logic - question handling
- TEL: Temporal Epistemic Logic - phase sequencing
- SDL: Standard Deontic Logic - obligations/permissions
- DEL: Dynamic Epistemic Logic - action modalities
Justification Logic (JL)
# Justification terms
[h]:context(task_n) # Handoff h justifies task context
[v]:verified(phase_n) # Verification v justifies completion
[p]:plan(tasks) # Plan p justifies task list
# Evidence production
[read(f)]exists e. [e]:content(f)
[verify(c)]exists v. [v]:pass(c) | [v]:fail(c)
# Handoff chain: evidence propagates
[h_n]:complete(task_n) -> [h_{n+1}]:context(task_{n+1})
proceed(task) <-> exists h. [h]:validated
Inferential Erotetic Logic (IEL)
# Mode and blocker questions
?{direct, orchestration} # Mode selection
?{continue, retry, ask_user} # Blocker resolution
mismatch(plan, reality) -> ?{how_proceed}
no_validation -> ?{run_validation_first}
Temporal Epistemic Logic (TEL)
# File reading constraints
[](mentioned(f) -> <>read_fully(f)) # Eventually read
[](mentioned(f) -> not spawn U read_fully(f)) # No spawn until read
[](partial_read(f) -> false) # Partial reads forbidden
# Phase sequencing
[](phase(n) -> P(phase(n-1) & verified(n-1))) # Verified before next
[](automated_pass -> <>manual_verify) # Automated gates manual
[](manual_pass(n) -> <>phase(n+1)) # Manual gates next phase
# Handoff persistence
[](handoff_created(h) -> []exists_on_disk(h)) # Survives compaction
# Termination
<>(all_complete | abandoned)
Standard Deontic Logic (SDL)
# Reading obligations
O(read_fully(plan))
O(read_fully(f)) <- mentioned_in_plan(f)
O(check_existing_checkmarks)
F(partial_read)
# Verification obligations
O(run_automated) <- impl_complete
O(pause_for_manual) <- automated_pass
O(present_manual_checklist)
F(checkoff_manual) <- not user_confirmed
# Mode selection
O(orchestration) <- tasks >= 4
P(direct) <- tasks <= 3
O(respect_user_preference)
# Orchestration obligations
O(read_previous_handoff) <- exists_handoff(task_{n-1})
O(create_handoff) <- agent_completes
O(update_ledger) <- task_complete
F(batch_tasks) # One agent per task
F(proceed_on_mismatch) <- not user_guidance
Dynamic Epistemic Logic (DEL)
# Implementation actions
[read(plan)]K(tasks) & K(phases) & K(criteria)
[read(handoff_n)]K(context_{n+1})
[spawn(agent, task)]<>result(agent)
[verify(c)](K(pass) | K(fail))
# Composed workflows
[select_direct][implement ; verify_auto ; present_manual ; wait]*
[select_orchestration][prepare ; spawn ; wait ; read_handoff ; update]*
# Recovery
[compaction ; read_ledger ; list_handoffs ; read_last]resume
# Mismatch
[detect_mismatch ; stop ; present ; wait]proceed_or_abort
Bridge Principles
# Evidence persistence (JL-TEL)
[h]:context(n) -> [][h]:context(n)
# Evidence obligations (JL-SDL)
O(exists h. [h]:validated) <- pre_implement
O(exists v. [v]:pass(auto)) <- pre_manual
# Handoff chain (full integration)
[h_n]:complete(n) -> O([spawn]<>[h_{n+1}]:context(n+1))
compaction -> (forall h. persists(h))
State Machine
INIT --> READ_PLAN --> MODE_SELECT --+--> DIRECT: [IMPL -> AUTO -> MANUAL -> WAIT]*
|
+--> ORCHESTRATION: [PREP -> SPAWN -> WAIT -> HANDOFF]*
|
v
COMPLETE
Output Schema
handoff_path: "thoughts/handoffs/<session>/task-[NN]-[desc].md"
schema:
required: [status, task_desc, files_modified[], verification_results, context_for_next]
optional: [blocker, decisions[], open_questions[]]
tracking:
plan: "- [x] Task N: description"
ledger: "[x] Task N"
Prose (Where Logic Insufficient)
Mode Selection
| Tasks | Context Critical | Mode |
|---|---|---|
| 1-3 | No | Direct |
| 1-3 | Yes | Orchestration |
| 4+ | Any | Orchestration |
User preference overrides.
Templates
Mismatch:
Issue in Phase [N]:
Expected: [plan says]
Found: [actual]
How should I proceed?
Manual Verification Pause:
Phase [N] Complete - Ready for Manual Verification
Automated passed: [list]
Please verify: [manual items from plan]
Let me know when done.
Agent Spawn:
Task(subagent_type="general-purpose", model="claude-opus-4-5-20251101", prompt="""
[implement_task SKILL.md]
## Context
- Ledger: [content]
- Plan: [section]
- Task: [N]/[Total]: [desc]
- Previous Handoff: [content or "first task"]
- Handoff Dir: thoughts/handoffs/<session>/
""")
Recovery (post-compaction):
- Ledger auto-loaded by SessionStart
ls thoughts/handoffs/<session>/- Read last handoff
- Resume next task
Validity Constraints
forall phase. has_auto_criteria(phase) & has_manual_criteria(phase)
forall task. one_agent_per_task(task)
forall h. on_disk(h) -> recoverable(h)
compaction -> (forall h. persists(h))
forall i < j. completed(task_i) before started(task_j)
More by parcadei
View all skills by parcadei →You might also like
flutter-development
aj-geddes
Build beautiful cross-platform mobile apps with Flutter and Dart. Covers widgets, state management with Provider/BLoC, navigation, API integration, and material design.
ui-ux-pro-max
nextlevelbuilder
"UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient."
drawio-diagrams-enhanced
jgtolentino
Create professional draw.io (diagrams.net) diagrams in XML format (.drawio files) with integrated PMP/PMBOK methodologies, extensive visual asset libraries, and industry-standard professional templates. Use this skill when users ask to create flowcharts, swimlane diagrams, cross-functional flowcharts, org charts, network diagrams, UML diagrams, BPMN, project management diagrams (WBS, Gantt, PERT, RACI), risk matrices, stakeholder maps, or any other visual diagram in draw.io format. This skill includes access to custom shape libraries for icons, clipart, and professional symbols.
godot
bfollington
This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.
nano-banana-pro
garg-aayush
Generate and edit images using Google's Nano Banana Pro (Gemini 3 Pro Image) API. Use when the user asks to generate, create, edit, modify, change, alter, or update images. Also use when user references an existing image file and asks to modify it in any way (e.g., "modify this image", "change the background", "replace X with Y"). Supports both text-to-image generation and image-to-image editing with configurable resolution (1K default, 2K, or 4K for high resolution). DO NOT read the image file first - use this skill directly with the --input-image parameter.
pdf-to-markdown
aliceisjustplaying
Convert entire PDF documents to clean, structured Markdown for full context loading. Use this skill when the user wants to extract ALL text from a PDF into context (not grep/search), when discussing or analyzing PDF content in full, when the user mentions "load the whole PDF", "bring the PDF into context", "read the entire PDF", or when partial extraction/grepping would miss important context. This is the preferred method for PDF text extraction over page-by-page or grep approaches.
Related MCP Servers
Browse all serversBMAD streamlines agile project management by uniting business and development teams for efficient delivery using agile p
Streamline your team software process with Spec-Driven Development, optimizing the software development life cycle using
Streamline your software development life cycle with Spec-Driven Development: organized specs, template-driven code, and
Spec-Driven Development integrates with IBM DOORS software to track software licenses, automate requirements, and enforc
Break down complex problems with Sequential Thinking, a structured tool and step by step math solver for dynamic, reflec
Build persistent semantic networks for enterprise & engineering data management. Enable data persistence and memory acro
Stay ahead of the MCP ecosystem
Get weekly updates on new skills and servers.