plan-work

Name: plan-work
Availability: InStock
Author: Nymbo

Research repository state and document options and risks before coding.

Updated Aug 27, 2026

Search Tags:#planning #analysis #Q&A #risk #implementation-plan #repo-research

Ready to run

npx skills add https://github.com/Nymbo/Skills --skill plan-work

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-work
Source: https://github.com/Nymbo/Skills/tree/main/plan-work
Command: npx skills add https://github.com/Nymbo/Skills --skill plan-work

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Planning work before coding helps teams research the repo, analyze options and risks, and ask clarifying questions before proposing an implementation plan.

Core Features & Use Cases

Research: Review repo guidance, entrypoints, and owners to ground decisions.
Analysis: Explicitly evaluate options and risks; document tradeoffs.
Q&A gate: Gather missing inputs via clarifying questions before proceeding.
Implementation Planning: Produce a concrete plan with milestones and success criteria.

Quick Start

Start a plan when asked for a plan, design/approach, scope breakdown, or implementation steps.

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

An implementation plan grounds decisions in repository reality by researching the codebase, analyzing options and risks, and documenting tradeoffs before writing code. Start by reviewing repo guidance, existing architecture, and constraints to identify viable approaches and potential blockers.

What should I research in my repository before planning work?▼

Research repo entrypoints, ownership, existing patterns, and constraints. Review guidance documents, dependency structures, and current state to ground planning decisions. This context prevents proposing approaches that conflict with existing architecture or project restrictions.

Why ask clarifying questions before proposing an implementation approach?▼

Clarifying questions surface missing requirements, constraints, and priorities that affect plan validity. Gathering these inputs upfront prevents rework and ensures the proposed implementation steps align with actual project needs and repository state.

How do I document risks and tradeoffs in a work plan?▼

Explicitly evaluate each option's tradeoffs, limitations, and risks. Document known constraints, dependencies, and failure modes alongside implementation steps so teams understand consequences before committing to an approach.

What's the output of a concrete implementation plan?▼

A concrete plan includes scope breakdown, milestones, success criteria, identified risks, and step-by-step implementation approach. It serves as a shared reference for execution and risk management across the team.