@webpresso/plugin-claude 0.0.4

package/skills/plan-refine/SKILL.md

@@ -0,0 +1,50 @@
+---
+type: skill
+slug: plan-refine
+title: Plan Refinement Methodology
+status: active
+scope: repo
+applies_to: [agents]
+related: []
+created: "2026-05-07"
+last_reviewed: "2026-07-03"
+name: plan-refine
+description: "Blueprint hardening: fact-check assumptions, run plan reviews, split parallel tasks, and lock verification."
+---
+
+# Plan Refinement Methodology
+
+Use when a blueprint or implementation plan needs fact-checking, architecture hardening, parallel task shaping, or review consolidation before execution.
+
+## Core principle
+
+A plan is only as strong as its weakest unchecked assumption and only as fast as its coarsest task granularity.
+
+## Required workflow
+
+1. **Technology fact-check.** Verify API, version, runtime, platform, and package claims against official/upstream sources when external behavior matters.
+2. **Codebase verification.** Confirm file paths, exports, existing patterns, dependency availability, and local command surfaces in the repo.
+3. **Architecture review.** Challenge race conditions, error cascades, ownership boundaries, concurrency, auth/session edges, public-package leakage, and unnecessary abstractions.
+4. **Plan-review lenses.** Folded `/autoplan`: run the relevant CEO/founder, design, engineering, and DevEx review lenses; consolidate keep/change/drop decisions, unresolved taste calls, tests, and go/no-go.
+5. **Blueprint enforcement.** Split tasks for independent execution, declare dependencies, identify file conflicts, require TDD/proof steps, and preserve acceptance criteria.
+6. **Apply and record.** Update edge cases, risks, technology choices, cross-plan references, and verification gates. Do not edit implementation code during plan refinement.
+
+## Mandatory gates
+
+- Apply DRY, SOLID, YAGNI, and KISS; reject speculative abstractions.
+- Choose the most elegant and durable solution the constraints allow, not merely a correct one: prefer deleting/reusing over adding, shrink public/export surface to the minimum real consumers require, keep the change scoped to one coherent idea, and reject the heavier option even when it works — record in the plan why the chosen shape is the durable one.
+- For package, catalog, generated-surface, or release changes, require package-surface and public-content checks.
+- Prefer deletion/reuse over new layers or dependencies.
+- Stop on unverified external claims, unresolved shared-file conflicts, or missing authority for destructive work.
+
+## Output
+
+Return a concise plan review with:
+
+- verdict: ready / ready with edits / blocked
+- material corrections with evidence
+- task/dependency changes needed for parallel execution
+- required tests and audits
+- residual risks or explicit blockers
+
+For the full historical checklist and examples, read `references/full-methodology.md` only when deeper plan surgery is needed.