skills.rest
jMerta
jMertaCOMMUNITY
Explore all skills by this author →
GitHub

plan-work

Research repositories, analyze options and risks, and ask clarifying questions before coding.

130|15|Updated Dec 14, 2025
Search Tags:#workflow#planning#research#analysis#implementation plan#Q&A
One-click install
npx skills add https://github.com/jMerta/codex-skills --skill plan-work-jmerta
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-work
Source: https://github.com/jMerta/codex-skills/tree/main/plan-work
Command: npx skills add https://github.com/jMerta/codex-skills --skill plan-work-jmerta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams plan work before coding by requiring repo research, risk analysis, and clarifying questions prior to creating implementation plans.

Core Features & Use Cases

  • Structured planning workflow: research the current state, analyze options and risks, and surface clarifying questions before committing to implementation.
  • Guidance for entrypoints, ownership, and code paths to ensure plan is grounded in repo reality.
  • Use Case: When a user requests a plan, design/approach, scope breakdown, or implementation steps, generate a clear, executable plan.

Quick Start

Use the plan-work skill to prepare a plan for the current project before starting any coding.

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?▼

To create an implementation plan, conduct repo research, analyze risks and options, and ask clarifying questions to ensure zero unknowns before execution. This structured planning workflow grounds your approach in repo reality.

What is the best way to analyze risks before starting software implementation?▼

Analyzing risks before implementation involves researching the current repo state and evaluating options to surface decisions. This process identifies open questions early, ensuring your scope breakdown is executable.

How do I identify open questions and decisions for a software design approach?▼

Identify open questions by using plan gates during your design workflow. This approach maps entrypoints and code paths, surfacing necessary clarifications before committing to implementation steps.

Do I need external tooling to generate a scope breakdown for my project?▼

No external tooling is required to generate a scope breakdown. The planning workflow relies on internal analysis of repo reality and Q&A gates to guide structured preparation before execution.

When do I need a structured planning workflow for software engineering tasks?▼

You need a structured planning workflow when requesting a design, scope breakdown, or implementation steps. It ensures repo research and risk analysis are completed prior to coding, preventing unknowns during execution.

Related Skills

Explore More Software Engineering Skills→
refactory-langrefactory-lang

speckit-workflows.baseline

Generate baseline-spec.md and current-state.md from codebase and git history.

Official
Advanced
eddieluengeddielueng
1

writing-plans

Generate step-by-step implementation plans with TDD tasks from requirements specs.

Community
Intermediate
bcbeidelbcbeidel
1

map-vs-territory

Identify gaps between mental models and reality using a seven-step workflow.

Community
Intermediate
Poom5741Poom5741

gsd-quick

Coordinate ad-hoc tasks with atomic commits and STATE.md progress tracking.

Community
Advanced