skills.rest
carlos18bp
carlos18bpCOMMUNITY
Explore all skills by this author →
GitHub

plan-task

Convert task descriptions into decision-complete implementation plans.

1|Updated Sep 6, 2024
Search Tags:#planning#task decomposition#test selection#repo inspection#implementation blueprint#migrations guidance#product-scope guardrails
One-click install
npx skills add https://github.com/carlos18bp/gym_project --skill plan-task-carlos18bp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-task
Source: https://github.com/carlos18bp/gym_project/tree/main/.agents/skills/plan-task
Command: npx skills add https://github.com/carlos18bp/gym_project --skill plan-task-carlos18bp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

plan-task eliminates the back-and-forth needed to clarify scope by turning an already-complete task description into a decision-complete implementation plan.

Core Features & Use Cases

  • Scope parsing without re-asking: Treats the provided task text ($ARGUMENTS) as the canonical specification and extracts objective, areas, constraints, and acceptance criteria.
  • Repo-aware planning: Maps the likely code/data flow impact by inspecting referenced areas and aligning with existing project conventions.
  • Execution-safe output: Produces a planning-only result (no file edits, no committing) that’s ready for a follow-up /implement step.

Quick Start

Invoke plan-task with the full task description in $ARGUMENTS, for example: /plan-task "refactor: extract the logic for computing totals into a reusable module without changing the UI".

Frequently Asked Questions about plan-task

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

FAQPage Schema
How do I convert a task brief into an implementation blueprint without re-asking for scope?▼

To convert a task brief into an implementation blueprint, provide the fully specified task description as input. The system parses the objective, constraints, and acceptance criteria to produce a decision-complete plan without requesting additional product scope.

How do I map change impact for a refactor by inspecting existing repository conventions?▼

Mapping change impact for a refactor involves inspecting referenced repository areas to trace data flow, APIs, state, and tests. This identifies affected components and aligns new modifications with existing project conventions.

What is the best way to plan migrations and choose defaults for unresolved tradeoffs during task decomposition?▼

Planning migrations and choosing defaults for unresolved tradeoffs requires analyzing the task brief against repository conventions. The system evaluates the impact map and selects safe defaults to output a decision-complete implementation plan.

Can I use this planning workflow for bug investigations without it modifying my repository files?▼

Yes, you can use this workflow for bug investigations safely. It is designed as a planning-only tool that analyzes the repository and returns a compact plan without executing file edits, committing changes, or altering your codebase.

Does task decomposition planning provide test selection guidance based on affected components?▼

Task decomposition planning includes test selection guidance by inspecting the repository's impact map. It identifies affected components and maps the necessary test coverage areas directly within the returned implementation blueprint.

Related Skills

Explore More Software Engineering Skills→
meta-pytorchmeta-pytorch
2.5k

work-on-issue

Parse GitHub issues into goals, acceptance criteria, and constraints.

Official
Intermediate
gesmith0606gesmith0606

gsd-quick

Execute small repository tasks with atomic commits and STATE.md tracking.

Community
Advanced
yanochka11yanochka11

pr-writer

Generate GitHub pull request descriptions from branch changes and git history.

Community
Advanced
SaturateSaturate

idea-refine

Generate 3-5 actionable options with tradeoffs and a Not Doing list.

Community
Advanced