← All creators

SandeepTakasi

User

Plan-first parallel execution for Claude Code: rigorous plan documents, wave-based subagent execution with disjoint file ownership, plan-conformance verification gates, and a reconcile loop. Nothing sails until it leaves the dock.

5 indexed · 0 Featured · 0 stars · avg score 73
Prolific

Categories

Indexed Skills (5)

AI & Automation Listed

replan

Surgically repair a stale or blocked Drydock plan — re-verify its Assumptions Register against the current codebase, patch only the tasks invalidated by drift or deviations, and preserve the Decision Log and all completed-wave history. Invoke on a plan that is blocked, old, or whose assumptions no longer hold.

0 Updated yesterday
SandeepTakasi
Data & Documents Listed

planwright

Craft a rigorous, surgical implementation plan — phases, parallel waves, atomic tasks, right-sized model assignments, and verification gates — as a persistent plan document, without writing any implementation code. Use this skill whenever the user asks to "create a plan", "plan this feature/change", "break this down", "design phases and tasks", wants a task breakdown for subagent or parallel execution, or requests any multi-file change large enough that a plan should precede implementation — even if they never say the word "plan".

0 Updated yesterday
SandeepTakasi
DevOps & Infrastructure Listed

reconcile

Close out a completed Drydock plan — consolidate the Deviation Log, diff the plan's assumptions against what execution actually revealed, and produce proposed (never auto-applied) updates to project docs like CLAUDE.md, ADRs, and architecture notes so the next plan starts from reality instead of stale context. Invoke after the final wave passes wavecheck.

0 Updated yesterday
SandeepTakasi
Testing & QA Listed

seatrial

Execute a Drydock plan's Testing Gate — drive its written end-to-end cases against the running app through Playwright MCP, capture the declared evidence per case, generate re-runnable Playwright spec files, and emit a go/no-go verdict sheet fit for QA handoff. Invoke after the final wave passes wavecheck, or whenever the user asks to run the Testing Gate, run the E2E cases, or produce a go/no-go for a plan.

0 Updated yesterday
SandeepTakasi
Data & Documents Listed

wavecheck

Verify a completed execution wave against its Drydock plan — audit that each task's diff stays inside its owned files, acceptance criteria hold, forbidden items were respected, and nothing outside the plan changed. Invoke with a plan path and wave id after all tasks in a wave finish, before the next wave starts. Emits PASS or BLOCK and appends the report to the plan.

0 Updated yesterday
SandeepTakasi

Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.