Executing Plans Inline
obra/superpowers
Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.
Create a markdown document that describes a specific task along with concise implementation plan, at issues/YYYYMMDD-blah-blah.md, where YYYYMMDD is based on today's date.
Install Make Issue Spec
$ npx skills add pchalasani/claude-code-tools --skill make-issue-spec -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install pchalasani/claude-code-tools make-issue-spec --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/pchalasani/claude-code-tools.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/workflow/skills/make-issue-spec .claude/skills/make-issue-spec && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "make-issue-spec" agent skill from https://github.com/pchalasani/claude-code-tools/tree/main/plugins/workflow/skills/make-issue-spec into .claude/skills/make-issue-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "make-issue-spec", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/pchalasani/claude-code-tools/tree/main/plugins/workflow/skills/make-issue-specType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add pchalasani/claude-code-tools --skill make-issue-spec -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install pchalasani/claude-code-tools make-issue-spec --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pchalasani/claude-code-tools.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/workflow/skills/make-issue-spec .agents/skills/make-issue-spec && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "make-issue-spec" agent skill from https://github.com/pchalasani/claude-code-tools/tree/main/plugins/workflow/skills/make-issue-spec into .agents/skills/make-issue-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "make-issue-spec", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pchalasani/claude-code-tools --skill make-issue-spec -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install pchalasani/claude-code-tools make-issue-spec --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pchalasani/claude-code-tools.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/workflow/skills/make-issue-spec .cursor/skills/make-issue-spec && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "make-issue-spec" agent skill from https://github.com/pchalasani/claude-code-tools/tree/main/plugins/workflow/skills/make-issue-spec into .cursor/skills/make-issue-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "make-issue-spec", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/pchalasani/claude-code-tools.git --path plugins/workflow/skills/make-issue-spec--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add pchalasani/claude-code-tools --skill make-issue-spec -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install pchalasani/claude-code-tools make-issue-spec --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pchalasani/claude-code-tools.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/workflow/skills/make-issue-spec .gemini/skills/make-issue-spec && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "make-issue-spec" agent skill from https://github.com/pchalasani/claude-code-tools/tree/main/plugins/workflow/skills/make-issue-spec into .gemini/skills/make-issue-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "make-issue-spec", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install pchalasani/claude-code-tools make-issue-specInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add pchalasani/claude-code-tools --skill make-issue-spec -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/pchalasani/claude-code-tools.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/workflow/skills/make-issue-spec .github/skills/make-issue-spec && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "make-issue-spec" agent skill from https://github.com/pchalasani/claude-code-tools/tree/main/plugins/workflow/skills/make-issue-spec into .github/skills/make-issue-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "make-issue-spec", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pchalasani/claude-code-tools --skill make-issue-spec -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install pchalasani/claude-code-tools make-issue-spec --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pchalasani/claude-code-tools.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/workflow/skills/make-issue-spec .opencode/skills/make-issue-spec && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "make-issue-spec" agent skill from https://github.com/pchalasani/claude-code-tools/tree/main/plugins/workflow/skills/make-issue-spec into .opencode/skills/make-issue-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "make-issue-spec", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
make-issue-spec- GitHub stars
- 2k
- Token cost
- ~136 tokens
- SKILL.md length
- 58 words
- Files
- 1
- Skills in repo
- 17
- Repo updated
- First seen
- Licence
- MIT
At a glance
Create a markdown document that describes a specific task along with concise implementation plan, at issues/YYYYMMDD-blah-blah.md, where YYYYMMDD is based on today's date.
- Tasks that involve Planning
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Make Issue Spec is an agent skill from pchalasani/claude-code-tools. Create a markdown document that describes a specific task along with concise implementation plan, at issues/YYYYMMDD-blah-blah.md, where YYYYMMDD is based on today's date.
Its SKILL.md is about 140 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering Planning. The repository describes itself as: Practical productivity tools for Claude Code, Codex-CLI, and similar CLI coding agents. The licence is MIT.
When your agent uses it
- Tasks that involve Planning
Example prompts
- “/make-issue-spec”
What it can do on your machine
Read from SKILL.md and the folder at commit 0ca7320. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Make Issue Spec loads about 136 tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 58 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from pchalasani/claude-code-tools at commit 0ca7320, republished under its MIT licence (© pchalasani). 58 words, ~136 tokens.
Download SKILL.mdSave it as
.claude/skills/make-issue-spec/SKILL.md (or your agent's skills folder).- name
- make-issue-spec
- description
- Create a markdown document that describes a specific task along with concise implementation plan, at issues/YYYYMMDD-blah-blah.md, where YYYYMMDD is based on today's date.
make-issue-spec
There isn't a lot more to this than what the top level description says. The idea is for this issue spec to contain a clear specification of what is needed. Make sure to ask the user any questions for parts that you're not sure of or are under specified. Stage this in Git if you have permissions.
© pchalasani, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugins/workflow/skills/make-issue-spec of pchalasani/claude-code-tools.
Open the folder on GitHubat commit 0ca7320
Compare with similar skills
Make Issue Spec next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Make Issue Spec this skillpchalasani/claude-code-tools | 2k | — | ~136 | Automated safety check: Pass | MIT | |
| Executing Plans Inlineobra/superpowers | 296k | 2 repos | ~5.1k | Automated safety check: Pass | MIT | |
| Interview Meaddyosmani/agent-skills | 102k | 6 repos | ~3.8k | Automated safety check: Pass | MIT | |
| OpenSpec Guided OnboardingFission-AI/OpenSpec | 71k | 1 repos | ~4.5k | Automated safety check: Pass | MIT | |
| Writing Plansgeeksblabla/stateofdev.ma | 163 | 56 repos | ~661 | Automated safety check: Pass | None | |
| Subagent Driven DevelopmentAsvarox/allkaraoke | 261 | 37 repos | ~1.2k | Automated safety check: Pass | None |
Similar skills
Interview Me
addyosmani/agent-skills
Asks one question at a time, each with a best guess attached, until the agent is about 95 percent sure what you really want, before any plan, spec or code.
OpenSpec Guided Onboarding
Fission-AI/OpenSpec
Walks you through a complete OpenSpec workflow cycle with narration while doing real work in your codebase.
Writing Plans
geeksblabla/stateofdev.ma
A skill your agent uses when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file…
Subagent Driven Development
Asvarox/allkaraoke
A skill your agent uses when executing implementation plans with independent tasks in the current session
Planning With Files
jd-opensource/JoySafeter
Implements Manus-style file-based planning for complex tasks.
More from pchalasani/claude-code-tools
All 17 skills in this repoRemove AI Patterns
pchalasani/claude-code-tools
Remove AI-writing patterns ("AI-isms") from text using the avoid-ai-writing catalog (conorbronsdon/avoid-ai-writing).
Dynamic Workflow
pchalasani/claude-code-tools
Create, review, run, inspect, pause, resume, and cancel durable JavaScript workflows that coordinate multiple headless Codex agents.
Voxtype Install
pchalasani/claude-code-tools
Guide the user through installing, configuring, and launching voxtype — local on-device voice dictation (speech-to-text that types wherever the cursor is).
Agent Style
pchalasani/claude-code-tools
Literature-backed English technical-prose writing rules (agent-style, 21 rules).
Msg
pchalasani/claude-code-tools
Inter-agent communication via the msg CLI. An agent skill from pchalasani/claude-code-tools.
Tmux CLI
pchalasani/claude-code-tools
CLI utility to communicate with other CLI Agents or Scripts in other tmux panes; use it only when user asks you to communicate with other CLI Agents or Scripts in other tmux panes.
Related
Categories
Questions about Make Issue Spec
What does Make Issue Spec do?
Create a markdown document that describes a specific task along with concise implementation plan, at issues/YYYYMMDD-blah-blah.md, where YYYYMMDD is based on today's date. Make Issue Spec is an agent skill from pchalasani/claude-code-tools.md, where YYYYMMDD is based on today's date.
When should I use Make Issue Spec?
Make Issue Spec fits situations like: tasks that involve Planning.
How do I install Make Issue Spec in Claude Code?
Run `npx skills add pchalasani/claude-code-tools --skill make-issue-spec -a claude-code`. Or copy the skill folder (plugins/workflow/skills/make-issue-spec in pchalasani/claude-code-tools) into .claude/skills/make-issue-spec in your project. Claude Code loads it when a task matches its description.
How do I install Make Issue Spec in Codex?
Run `npx skills add pchalasani/claude-code-tools --skill make-issue-spec -a codex`. Or copy the skill folder (plugins/workflow/skills/make-issue-spec in pchalasani/claude-code-tools) into .agents/skills/make-issue-spec in your project. Codex loads it when a task matches its description.
Can I use Make Issue Spec in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add pchalasani/claude-code-tools --skill make-issue-spec -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/make-issue-spec, .gemini/skills/make-issue-spec, .github/skills/make-issue-spec and .opencode/skills/make-issue-spec in your project.
What does Make Issue Spec need to run?
SKILL.md names no scripts, command-line tools or credentials: Make Issue Spec is instructions for the agent only.
Does Make Issue Spec access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Make Issue Spec safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Make Issue Spec use?
Make Issue Spec is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Make Issue Spec use?
About 136 tokens (SKILL.md is roughly 544 characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Make Issue Spec?
Skills that share tags, products or a category with Make Issue Spec: Executing Plans Inline (obra/superpowers, 296k stars), Interview Me (addyosmani/agent-skills, 102k stars), OpenSpec Guided Onboarding (Fission-AI/OpenSpec, 71k stars) and Writing Plans (geeksblabla/stateofdev.ma, 163 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Make Issue Spec?
pchalasani (a GitHub user) maintains it in pchalasani/claude-code-tools, which has 2,009 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 5, 2026.
Source: pchalasani/claude-code-tools on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.