How do I install the Plan Task skill?

Run npx skillmds@latest add tomevault-io/plan-task in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Plan Task safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Plan Task?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Plan Task free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Plan Task?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Plan Task by tomevault-io — Agent Skill

Name: Plan Task
Author: tomevault-io

File contents

BEFORE ANYTHING ELSE, CHECK IF THE USER PROVIDED A DESCRIPTION AS AN ARGUMENT ($ARGUMENTS). IF THEY DID, USE THAT. IF NOT, ASK THE USER FOR A DETAILED DESCRIPTION OF WHAT THEY WANT. DO NOT PROCEED UNLESS YOU HAVE THE DESCRIPTION!

Create a plan for a feature or task. Produces a GitHub issue as the source of truth.

Procedure

Research - Explore codebase to understand scope and constraints
Draft - Create ./scratchpad/plan-<slug>.md with the template below (create the scratchpad directory if it doesn't exist: mkdir -p ./scratchpad)
Review - Present draft to user for feedback

Finalize - Once approved, create GitHub issue:

# Ensure label exists
gh label create "feature" --description "Feature request" --color "0E8A16" 2>/dev/null || true
gh issue create --title "<title>" --body-file ./scratchpad/plan-<slug>.md --label "feature"

Cleanup - Verify the issue was created successfully (gh issue view <number>), then delete the scratchpad file

Issue Template

The scratchpad file MUST follow this format to work with /workon:

## Summary

<1-3 sentence problem statement>

## Requirements

- [ ] Requirement 1
- [ ] Requirement 2
- [ ] Requirement 3

## Proposed Approach

<Brief description of the implementation strategy>

## Implementation Steps

- [ ] Step 1 - <description>
- [ ] Step 2 - <description>
- [ ] Step 3 - <description>

## Open Questions

- <Any unresolved decisions or unknowns>

---

## Workon Prompt

> **Start here:** <specific first action to take>
>
> **Key files:** `path/to/file1.rs`, `path/to/file2.rs`
>
> **Context:** <any important background needed to begin>

Notes

The "Workon Prompt" section is essential - it tells /workon how to begin

Current Context

Open issues: !gh issue list --state open --limit 10 --json number,title --jq '.[] | "- #\(.number) \(.title)"' 2>/dev/null || echo "no issues"

Existing scratchpad plans: !ls -1 ./scratchpad/plan-*.md 2>/dev/null || echo "no drafts"

Project structure: !ls -1 -d */ 2>/dev/null | head -15 || echo "empty directory"

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: plan-taskdescription: Create a plan for a feature or task, producing a GitHub issue as source of truth Use when this capability is needed.---BEFORE ANYTHING ELSE, CHECK IF THE USER PROVIDED A DESCRIPTION AS AN ARGUMENT (`$ARGUMENTS`). IF THEY DID, USE THAT. IF NOT, ASK THE USER FOR A DETAILED DESCRIPTION OF WHAT THEY WANT. DO NOT PROCEED UNLESS YOU HAVE THE DESCRIPTION!Create a plan for a feature or task. Produces a GitHub issue as the source of truth.## Procedure1. **Research** - Explore codebase to understand scope and constraints2. **Draft** - Create `./scratchpad/plan-<slug>.md` with the template below (create the `scratchpad` directory if it doesn't exist: `mkdir -p ./scratchpad`)3. **Review** - Present draft to user for feedback4. **Finalize** - Once approved, create GitHub issue: ```bash # Ensure label exists gh label create "feature" --description "Feature request" --color "0E8A16" 2>/dev/null || true gh issue create --title "<title>" --body-file ./scratchpad/plan-<slug>.md --label "feature" ```5. **Cleanup** - Verify the issue was created successfully (`gh issue view <number>`), then delete the scratchpad file## Issue TemplateThe scratchpad file MUST follow this format to work with `/workon`:```markdown## Summary<1-3 sentence problem statement>## Requirements- [ ] Requirement 1- [ ] Requirement 2- [ ] Requirement 3## Proposed Approach<Brief description of the implementation strategy>## Implementation Steps- [ ] Step 1 - <description>- [ ] Step 2 - <description>- [ ] Step 3 - <description>## Open Questions- <Any unresolved decisions or unknowns>---## Workon Prompt> **Start here:** <specific first action to take>>> **Key files:** `path/to/file1.rs`, `path/to/file2.rs`>> **Context:** <any important background needed to begin>```## Notes- The "Workon Prompt" section is essential - it tells `/workon` how to begin## Current ContextOpen issues:!`gh issue list --state open --limit 10 --json number,title --jq '.[] | "- #\(.number) \(.title)"' 2>/dev/null || echo "no issues"`Existing scratchpad plans:!`ls -1 ./scratchpad/plan-*.md 2>/dev/null || echo "no drafts"`Project structure:!`ls -1 -d */ 2>/dev/null | head -15 || echo "empty directory"`---> Converted and distributed by [TomeVault](https://tomevault.io/claim/jordond) — claim your Tome and manage your conversions.

Frequently asked questions

Plan Task