How do I install the Dev skill?

Run npx skillmds@latest add dannysmith/dev 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.

This skill has not completed SkillMD's automated safety review yet. Capability flags: executes scripts. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Dev?

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.

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

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

Dev by dannysmith — Agent Skill

Name: Dev
Rating: 4.2 (5 reviews)
Author: dannysmith

Dev

This skill should be used when the user invokes "/personal:dev" with a subcommand. Subcommands: init (project + task setup), new (create task from description or GH issue), complete (finish a task), renumber (reorder task priorities), prime (load project context).

dannysmith Updated Sep 10, 2026

File contents

Dev Utilities

Project development utilities for initialisation, task management, and context priming. Designed for any dev project. Tasks are tracked as markdown files: todo tasks in docs/tasks-todo/task-NUMBER-name.md, completed tasks in docs/tasks-done/YYYY-MM-DD-task-NUMBER-name.md. If this project has not been initialised with this system yet, suggest the user runs /personal:dev init first.

Full user input

$ARGUMENTS

Important: executing bundled scripts

Scripts in scripts/ are executable with shebangs. Execute them directly — never prepend bash, sh, or any interpreter. For example: scripts/init-project.sh not bash scripts/init-project.sh.

Subcommands

The first word of the user input above is the subcommand. Everything after it is context for that subcommand. If no argument was provided, list the available subcommands and ask the user which they want.

init

Initialise or update a project's AI boilerplate and task management structure.

Two phases:

Execute: scripts/init-project.sh
Read and follow the AI instructions in references/init.md

new

Create a new task file in docs/tasks-todo/.

Read and follow references/new.md. The context for the new task is everything after "new" in the user input above.

complete

Complete a task by moving it from docs/tasks-todo/ to docs/tasks-done/ with a date prefix.

The task identifier is the word immediately after "complete" in the user input.

Execute: scripts/complete-task.sh <task-identifier>

Report the result to the user.

renumber

Renumber prioritised tasks to start from 1 with no gaps.

Execute: scripts/renumber-tasks.sh

Report the result to the user.

prime

Prime the current session with essential project context.

Read and follow references/prime.md. The context/focus area is everything after "prime" in the user input above (if anything).

---name: devdescription: This skill should be used when the user invokes "/personal:dev" with a subcommand. Subcommands: init (project + task setup), new (create task from description or GH issue), complete (finish a task), renumber (reorder task priorities), prime (load project context).---# Dev UtilitiesProject development utilities for initialisation, task management, and context priming.Designed for any dev project. Tasks are tracked as markdown files: todo tasks in`docs/tasks-todo/task-NUMBER-name.md`, completed tasks in`docs/tasks-done/YYYY-MM-DD-task-NUMBER-name.md`. If this project has not been initialisedwith this system yet, suggest the user runs `/personal:dev init` first.## Full user input$ARGUMENTS## Important: executing bundled scriptsScripts in `scripts/` are executable with shebangs. Execute them directly — neverprepend `bash`, `sh`, or any interpreter. For example: `scripts/init-project.sh` not`bash scripts/init-project.sh`.## SubcommandsThe first word of the user input above is the subcommand. Everything after it is contextfor that subcommand. If no argument was provided, list the available subcommands and askthe user which they want.### initInitialise or update a project's AI boilerplate and task management structure.Two phases:1. Execute: `scripts/init-project.sh`2. Read and follow the AI instructions in [references/init.md](references/init.md)### newCreate a new task file in `docs/tasks-todo/`.Read and follow [references/new.md](references/new.md). The context for the new task iseverything after "new" in the user input above.### completeComplete a task by moving it from `docs/tasks-todo/` to `docs/tasks-done/` with a date prefix.The task identifier is the word immediately after "complete" in the user input.Execute: `scripts/complete-task.sh <task-identifier>`Report the result to the user.### renumberRenumber prioritised tasks to start from 1 with no gaps.Execute: `scripts/renumber-tasks.sh`Report the result to the user.### primePrime the current session with essential project context.Read and follow [references/prime.md](references/prime.md). The context/focus area iseverything after "prime" in the user input above (if anything).

Frequently asked questions

Dev