new-task

Creates a plan.html requirements document for a new software task.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/mistakenot/skills --skill new-task-mistakenot
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: new-task
Source: https://github.com/mistakenot/skills/tree/main/plugins/planning-workflow/skills/new-task
Command: npx skills add https://github.com/mistakenot/skills --skill new-task-mistakenot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Starting a new feature or fix without written requirements leads to scope creep and misaligned expectations. This Skill turns a user's feature or fix description into a structured plan.html document with a Requirements tab, giving the task a clear problem statement, goals, and boundaries before any code is written. ## Core Features & Use Cases - Sequential task IDs: Scans docs/tasks/ for existing folders and assigns the next 3-digit ID with a kebab-case name derived from the user's description. - Structured requirements capture: Creates plan.html via the rich-doc skill with Problem, Goals, Out of Scope, and Open Questions sections following defined content guidelines. - Decision gating: Records unresolved load-bearing decisions as gating <pd-question> elements with recommended answers, so later execution stages cannot run past unmade decisions. - Use Case: A user says "create a task for adding team settings to the dashboard" and receives docs/tasks/043-add-team-settings/plan.html with a populated Requirements tab, ready for review before running /new-solution. ## Quick Start Ask the agent to create a new task for the feature or fix you want to plan, and it will generate a plan.html requirements document for your review.

Frequently Asked Questions about new-task

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

FAQPage Schema
How do I create a requirements document for a new software task?▼

Describe the feature or fix you want to plan and invoke the new-task skill. It scans docs/tasks/ for the next sequential ID, creates a task folder, and generates plan.html with a Requirements tab covering Problem, Goals, Out of Scope, and Open Questions.

How are task IDs and folder names assigned?▼

The skill scans docs/tasks/ for existing folders and assigns the next 3-digit sequential ID, starting at 001 if none exist. The folder name combines the ID with a short kebab-case name derived from your description, such as 043-add-team-settings.

What happens to unresolved questions in the requirements?▼

Load-bearing decisions are recorded as pd-question elements with a recommendedAnswer, which gate the document so later execution stages cannot proceed past them. Assumptions safe to proceed on stay as prose Open Questions bullets that do not block the workflow.

When should I use new-task-quick instead of new-task?▼

Use new-task-quick when you want all three planning stages run unattended in one pass, pausing only for open questions. Use new-task when you want to review the requirements document before moving to the solution stage, since new-task hard-stops after creating plan.html.

Does new-task work without the rich-doc skill installed?▼

No. Step 6 of the process loads the rich-doc skill to create plan.html, including fetching llms.txt for component references. Without rich-doc available, the plan.html generation step cannot complete as specified.