implement-plan-micro
Implements technical plans using formal logic to verify and validate progress.
Install
mkdir -p .claude/skills/implement-plan-micro && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/1120" && unzip -o skill.zip -d .claude/skills/implement-plan-micro && rm skill.zipInstalls to .claude/skills/implement-plan-micro
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Implement technical plans from thoughts/shared/plans with verificationKey capabilities
- →Execute multi-step development plans
- →Verify task completion via evidence-based gating
- →Perform contextual reasoning using modal logic
- →Validate phase sequencing before implementation
How it works
Applies a fusion of modal logics to validate state transitions and evidence before committing to each code change.
Inputs & outputs
When to use implement-plan-micro
- →Run complex multi-step refactoring
- →Execute automated feature implementation
- →Ensure task verification before handoff
- →Debug plan implementation blockers
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)
When not to use it
- →Executing non-technical tasks
- →High-level strategy discussions lacking concrete code goals
Limitations
- →Rigid adherence to verified phases
- →Requires clear pre-existing plans
How it compares
It requires logical justification and evidence for every step, unlike generic prompt-based code implementation.
Compared to similar skills
implement-plan-micro side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| implement-plan-micro (this skill) | 3 | 7mo | No flags | Advanced |
| command-development | 16 | 8mo | Review | Intermediate |
| skill-forge | 11 | 9mo | Review | Intermediate |
| codex-skill | 12 | 5mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by parcadei
View all by parcadei →You might also like
command-development
anthropics
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
skill-forge
WilliamSaysX
Automated skill creation workshop with intelligent source detection, smart path management, and end-to-end workflow automation. This skill should be used when users want to create a new skill or convert external resources (GitHub repositories, online documentation, or local directories) into a skill. Automatically fetches, organizes, and packages skills with proactive cleanup management.
codex-skill
feiskyer
Use when user asks to leverage codex, gpt-5, or gpt-5.1 to implement something (usually implement a plan or feature designed by Claude). Provides non-interactive automation mode for hands-off task execution without approval prompts.
agent-factory
alirezarezvani
Claude Code agent generation system that creates custom agents and sub-agents with enhanced YAML frontmatter, tool access patterns, and MCP integration support following proven production patterns
subagent-driven-development
davila7
Use when executing implementation plans with independent tasks in the current session
peekaboo
openclaw
Capture and automate macOS UI with the Peekaboo CLI.