CCPM Project Management
automazeio/ccpm
Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.
Runs multi step work the way a careful senior engineer would.
Install Project Workflow
$ npx skills add waynesutton/builder-skills --skill project-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install waynesutton/builder-skills project-workflow --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/waynesutton/builder-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/project-workflow .claude/skills/project-workflow && 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 "project-workflow" agent skill from https://github.com/waynesutton/builder-skills/tree/main/skills/project-workflow into .claude/skills/project-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-workflow", 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/waynesutton/builder-skills/tree/main/skills/project-workflowType 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 waynesutton/builder-skills --skill project-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install waynesutton/builder-skills project-workflow --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/waynesutton/builder-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/project-workflow .agents/skills/project-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "project-workflow" agent skill from https://github.com/waynesutton/builder-skills/tree/main/skills/project-workflow into .agents/skills/project-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-workflow", 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 waynesutton/builder-skills --skill project-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install waynesutton/builder-skills project-workflow --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/waynesutton/builder-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/project-workflow .cursor/skills/project-workflow && 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 "project-workflow" agent skill from https://github.com/waynesutton/builder-skills/tree/main/skills/project-workflow into .cursor/skills/project-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-workflow", 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/waynesutton/builder-skills.git --path skills/project-workflow--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 waynesutton/builder-skills --skill project-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install waynesutton/builder-skills project-workflow --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/waynesutton/builder-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/project-workflow .gemini/skills/project-workflow && 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 "project-workflow" agent skill from https://github.com/waynesutton/builder-skills/tree/main/skills/project-workflow into .gemini/skills/project-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-workflow", 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 waynesutton/builder-skills project-workflowInstalls 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 waynesutton/builder-skills --skill project-workflow -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/waynesutton/builder-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/project-workflow .github/skills/project-workflow && 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 "project-workflow" agent skill from https://github.com/waynesutton/builder-skills/tree/main/skills/project-workflow into .github/skills/project-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-workflow", 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 waynesutton/builder-skills --skill project-workflow -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install waynesutton/builder-skills project-workflow --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/waynesutton/builder-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/project-workflow .opencode/skills/project-workflow && 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 "project-workflow" agent skill from https://github.com/waynesutton/builder-skills/tree/main/skills/project-workflow into .opencode/skills/project-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-workflow", 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
project-workflow- GitHub stars
- 404
- Token cost
- ~1.1k tokens
- SKILL.md length
- 593 words
- Files
- 5 (incl. references, assets)
- Skills in repo
- 17
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Runs multi step work the way a careful senior engineer would.
- Works in 6 steps: Triage. Read the request and the code… → PRD. Write prds/.md from the template.… → Track. Add the work to task.md under ##… → …
- A task spans several files
- SKILL.md covers The loop, Triage, PRD and Task tracking, plus 4 more sections
- Calls git
What it does
Project Workflow is an agent skill from waynesutton/builder-skills. Runs multi step work the way a careful senior engineer would. Triage before code, a short PRD in prds/, task.md kept current, docs synced after, and lessons recorded when a mistake repeats. Use when a task spans several files or steps, changes architecture, needs a plan the user can review, or when the user says "write a PRD", "plan this", "track this in task.md", or "what did we learn".
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files and assets (for example `agents/openai.yaml` and `references/prd-template.md`).
It sits in Product & Project Management, covering PRD writing. The repository describes itself as: Builder skills for Convex apps. Convex patterns plus a PRD, task.md, changelog, and files.md workflow for Claude Code, Codex, Cursor, and OpenCode. The licence is Apache-2.0.
When your agent uses it
- A task spans several files
- Changes architecture
- Needs a plan the user can review
- The user says write a PRD
Example prompts
- “write a PRD”
- “plan this”
- “track this in task.md”
- “/project-workflow”
Requirements
- Node.js
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Triage. Read the request and the code before touching anything.
- PRD. Write prds/.md from the template. Share it if the plan has a real choice in it.
- Track. Add the work to task.md under ## To Do. Move items as they land.
- Build. Small commits worth of change at a time. Verify each step.
- Sync docs. Hand off to the project-docs skill to update task.md, changelog.md, files.md.
- Learn. If the user corrected the same thing twice, add a line to prds/lessons.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 82d1ce2. 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
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
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
Project Workflow loads about 1.1k tokens when it runs, and up to ~1.6k if it reads all its reference files. Until then it costs about 102 tokens; SKILL.md has 593 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 waynesutton/builder-skills at commit 82d1ce2, republished under its Apache-2.0 licence (© waynesutton). 593 words, ~1,132 tokens.
Download SKILL.mdSave it as
.claude/skills/project-workflow/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- project-workflow
- description
- Runs multi step work the way a careful senior engineer would. Triage before code, a short PRD in prds/, task.md kept current, docs synced after, and lessons recorded when a mistake repeats. Use when a task spans several files or steps, changes architecture, needs a plan the user can review, or when the user says "write a PRD", "plan this", "track this in task.md", or "what did we learn".
Project workflow
One loop for any task bigger than a typo. Plan in a PRD, track in task.md, sync docs when done, write down what went wrong so it does not repeat.
Skip this for one file fixes. A typo, a copy change, a single obvious bug. Just fix those.
The loop
- Triage. Read the request and the code before touching anything.
- PRD. Write
prds/<slug>.mdfrom the template. Share it if the plan has a real choice in it. - Track. Add the work to
task.mdunder## To Do. Move items as they land. - Build. Small commits worth of change at a time. Verify each step.
- Sync docs. Hand off to the
project-docsskill to updatetask.md,changelog.md,files.md. - Learn. If the user corrected the same thing twice, add a line to
prds/lessons.md.
Triage
Before writing code, answer these in a few lines:
- What is missing, broken, or incomplete?
- What are two or three likely causes or approaches?
- Which one is most likely, and why?
- What is still unclear enough to ask about?
If the last answer is not empty, ask. One question, not five. Then wait.
For bugs, name the root cause before proposing the fix. A fix without a root cause is a guess.
PRD
Create prds/<feature-or-problem-slug>.md before non trivial work. Use the layout in references/prd-template.md.
Required sections:
- Problem (one paragraph)
- Root cause (bugs only)
- Proposed solution
- Files to change
- Edge cases
- Verification steps
- Task completion log
Metadata at the top, always in UTC:
Created: YYYY-MM-DD HH:mm UTC
Last Updated: YYYY-MM-DD HH:mm UTC
Status: Draft | In Progress | DoneKeep it short. A PRD that takes longer to write than the change did is too long. Two screens is plenty for most work.
PRDs are .md files and live in prds/. Old or sensitive PRDs move to prds/archive/.
Task tracking
task.md has three sections: ## To Do, ## In Progress, ## Completed.
- New work goes under To Do with a link to its PRD.
- Only one item In Progress at a time when possible.
- An item moves to Completed after verification, not after the edit.
- Completed entries carry a
YYYY-MM-DD HH:mm UTCtimestamp, the files touched, and the verification command or outcome.
Good entry:
- [x] 2026-09-15 18:40 UTC Fix duplicate heartbeat writes. prds/heartbeat-dedup.md. convex/stats.ts, src/hooks/usePageTracking.ts. Verified: npx convex dev clean, no OCC retries in dashboard for 10 min.Bad entry:
- [x] fixed heartbeatShow full SKILL.md (238 more words)Show less
Docs sync
After each feature or fix, task.md, changelog.md, and files.md have to agree with the code. Load the project-docs skill for the rules. In short:
changelog.mdfollows Keep a Changelog. Dates come fromgit log --date=short, never from memory.files.mdgets new files added and stale descriptions fixed.- Claims about what shipped come from the diff, not from the plan.
Execution style
- Keep the change set tight. The request sets the scope. Extra ideas go in the summary, not the diff. Load
avoid-feature-creepif scope starts to drift. - One subagent per research question when the task is large enough to benefit. Do not parallelize edits to the same file.
- Stop and re plan if the work stops making sense. Update the PRD, then continue.
- Before calling it done, ask: would a staff engineer approve this diff as is?
Learning loop
prds/lessons.md is a flat list. One line per lesson, newest at the bottom:
- 2026-09-15 Do not add `returns` validators that duplicate the schema doc shape; use a shared validator constant instead.Add a lesson when:
- the user corrects the same pattern a second time
- a verification step catches something the plan missed
- a tool or API behaved differently from the docs
Read prds/lessons.md at the start of any session in that repo.
Never
- Deploy, publish, commit, or push. The user does those.
- Mark a task done without running the verification step written in the PRD.
- Invent a date. Run
git logor use the current UTC time. - Write a PRD for a one line change.
© waynesutton, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files (references, assets) in skills/project-workflow of waynesutton/builder-skills.
- SKILL.md
- agents/openai.yaml
- assets/large-logo.png
- assets/small-logo.svg
- references/prd-template.md
Open the folder on GitHubat commit 82d1ce2
Compare with similar skills
Project Workflow 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 |
|---|---|---|---|---|---|---|
| Project Workflow this skillwaynesutton/builder-skills | 404 | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| CCPM Project Managementautomazeio/ccpm | 8.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Ralph Tui Create Beadssubsy/ralph-tui | 2.5k | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Trellis Brainstormanjiemo/SunnyBeach | 178 | 7 repos | ~4k | Automated safety check: Pass | Apache-2.0 | |
| Adversarial Speczscole/adversarial-spec | 556 | 1 repos | ~8.3k | Automated safety check: Notes | MIT | |
| Ralph Tui Create Beads Rustsubsy/ralph-tui | 2.5k | 1 repos | ~2.8k | Automated safety check: Pass | MIT |
Similar skills
Ralph Tui Create Beads
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution. An agent skill from subsy/ralph-tui.
Trellis Brainstorm
anjiemo/SunnyBeach
Guides collaborative requirements discovery before implementation.
Adversarial Spec
zscole/adversarial-spec
Iteratively refine a product spec by debating with multiple LLMs (GPT, Gemini, Grok, etc.) until all models agree.
Ralph Tui Create Beads Rust
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution using beads-rust (br CLI).
To Issues
ywwynm/EverythingDone
Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices.
More from waynesutton/builder-skills
All 17 skills in this repoConvex Agents
waynesutton/builder-skills
Builds AI agents on the Convex agent component: threads, messages, tools that call queries and mutations, streaming, RAG with vector search, and workflows for multi step jobs.
Convex Best Practices
waynesutton/builder-skills
Production patterns for Convex apps and the rules the @convex-dev/eslint-plugin enforces: validators, indexes, idempotent mutations, avoiding OCC conflicts, thin function wrappers, error handling.
Convex Component Authoring
waynesutton/builder-skills
Creates reusable Convex components with defineComponent, a clean client wrapper, their own schema, and an npm publish setup.
Convex Cron Jobs
waynesutton/builder-skills
Schedules work in Convex: cron jobs in convex/crons.ts, one off scheduled functions with runAfter and runAt, batching large jobs, and cancelling or inspecting the queue.
Convex HTTP Actions
waynesutton/builder-skills
Adds HTTP endpoints in convex/http.ts: webhook receivers with signature checks, REST style routes, CORS, auth headers, streaming responses, and file uploads over HTTP.
Convex Migrations
waynesutton/builder-skills
Changes a live Convex schema without downtime: make a field optional, backfill in batches, flip the validator, then clean up.
Related
Categories
Questions about Project Workflow
What does Project Workflow do?
Runs multi step work the way a careful senior engineer would. Project Workflow is an agent skill from waynesutton/builder-skills. Runs multi step work the way a careful senior engineer would.
When should I use Project Workflow?
Project Workflow fits situations like: A task spans several files; changes architecture; needs a plan the user can review; the user says write a PRD.
How do I install Project Workflow in Claude Code?
Run `npx skills add waynesutton/builder-skills --skill project-workflow -a claude-code`. Or copy the skill folder (skills/project-workflow in waynesutton/builder-skills) into .claude/skills/project-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Project Workflow in Codex?
Run `npx skills add waynesutton/builder-skills --skill project-workflow -a codex`. Or copy the skill folder (skills/project-workflow in waynesutton/builder-skills) into .agents/skills/project-workflow in your project. Codex loads it when a task matches its description.
Can I use Project Workflow 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 waynesutton/builder-skills --skill project-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/project-workflow, .gemini/skills/project-workflow, .github/skills/project-workflow and .opencode/skills/project-workflow in your project.
What does Project Workflow need to run?
Going by SKILL.md and its folder, Project Workflow needs the command-line tools its instructions call (git). Our summary lists: Node.js.
Does Project Workflow access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Project Workflow 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 Project Workflow use?
Project Workflow is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Project Workflow use?
About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 478 tokens, read only when the agent opens those files.
What are the alternatives to Project Workflow?
Skills that share tags, products or a category with Project Workflow: CCPM Project Management (automazeio/ccpm, 8.4k stars), Ralph Tui Create Beads (subsy/ralph-tui, 2.5k stars), Trellis Brainstorm (anjiemo/SunnyBeach, 178 stars) and Adversarial Spec (zscole/adversarial-spec, 556 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Project Workflow?
waynesutton (a GitHub user) maintains it in waynesutton/builder-skills, which has 404 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on September 28, 2026.
Source: waynesutton/builder-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.