implement_plan_micro

parcadei/continuous-claude-v3 · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/parcadei/continuous-claude-v3 --skill implement_plan_micro
0 commentsdiscussion
summary

Five modal logics via fusion with bridge principles:

skill.md

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):

  1. Ledger auto-loaded by SessionStart
  2. ls thoughts/handoffs/<session>/
  3. Read last handoff
  4. 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)
how to use implement_plan_micro

How to use implement_plan_micro on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add implement_plan_micro
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/parcadei/continuous-claude-v3 --skill implement_plan_micro

The skills CLI fetches implement_plan_micro from GitHub repository parcadei/continuous-claude-v3 and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/implement_plan_micro

Reload or restart Cursor to activate implement_plan_micro. Access the skill through slash commands (e.g., /implement_plan_micro) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.627 reviews
  • Neel Ramirez· Dec 16, 2024

    I recommend implement_plan_micro for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Aisha Khanna· Dec 12, 2024

    Useful defaults in implement_plan_micro — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Chaitanya Patil· Dec 8, 2024

    Useful defaults in implement_plan_micro — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Piyush G· Nov 27, 2024

    implement_plan_micro is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Min Bhatia· Nov 7, 2024

    Keeps context tight: implement_plan_micro is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Zaid Okafor· Nov 3, 2024

    implement_plan_micro is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Diego Patel· Oct 26, 2024

    implement_plan_micro is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Zaid Desai· Oct 22, 2024

    Keeps context tight: implement_plan_micro is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Shikha Mishra· Oct 18, 2024

    Keeps context tight: implement_plan_micro is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Neel Gill· Sep 17, 2024

    implement_plan_micro fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

showing 1-10 of 27

1 / 3