plan_work

Creates implementation plans through repo research, risk analysis, and structured estimation.

Updated Jan 14, 2026
One-click install
npx skills add https://github.com/jvsandhu/agentic-skills --skill plan-work-jvsandhu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan_work
Source: https://github.com/jvsandhu/agentic-skills/tree/main/skills/plan_work
Command: npx skills add https://github.com/jvsandhu/agentic-skills --skill plan-work-jvsandhu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Jumping into code without a plan leads to scope creep, missed edge cases, and rework. This Skill enforces a disciplined pre-coding workflow covering requirements analysis, repository research, risk assessment, and estimation. ## Core Features & Use Cases - Structured Planning Process: A five-step flow from requirements analysis through repo research, option analysis, risk assessment, and plan creation. - Risk Analysis Templates: Categorized risk tables (technical, dependency, time, scope, integration) with probability/impact ratings and mitigation plans. - Implementation Plan Template: Ready-to-use Markdown template covering scope, file changes, dependencies, timeline, and test strategy, plus T-shirt size estimation guidelines. - Use Case: Before adding a new API endpoint to an existing codebase, use this Skill to inspect current architecture patterns, list clarifying questions, evaluate two design alternatives, and produce a reviewed implementation plan. ## Quick Start Ask the agent to create an implementation plan for your feature, including repo research, risk analysis, and effort estimation before writing any code.

Frequently Asked Questions about plan_work

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an implementation plan before coding?

Follow a five-step flow: analyze requirements, research the existing repo structure, evaluate alternative approaches, assess risks, and write the plan with steps and timeline. Use the provided Markdown template covering scope, file changes, dependencies, and test strategy.

How to estimate software development tasks?

Use complexity-based estimation tiers: trivial tasks take under 1 hour, small tasks 1-4 hours, medium 4-8 hours, large 1-3 days, and XL over a week. Alternatively, apply T-shirt sizing (S/M/L) during the design review phase.

What should a technical risk analysis include?

A risk analysis should categorize risks as technical, dependency, time, scope, or integration related. Each risk entry needs a probability and impact rating, a description, mitigation steps, and a contingency plan if the risk materializes.

What questions should I ask before starting a coding task?

Ask about requirement completeness, edge cases, error states, UI mockups, accessibility needs, performance targets, backward compatibility, migration strategy, and deadlines. These clarifying questions prevent scope creep and rework.

When is a full design plan not needed?

Trivial changes like config updates or one-line fixes under an hour of work do not need a full RFC-style plan. The planning workflow is designed for features, refactors, and changes with architectural or integration impact.