New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Project Delivery

by cbrock84 in cbrock84/headcount

Plans and delivers a single project — scope, estimation, scheduling, critical path, tracking, and recovering when it slips.

MITAuto-check passed

Install Project Delivery

skills CLI
$ npx skills add cbrock84/headcount --skill project-delivery -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install cbrock84/headcount project-delivery --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/pmo/skills/project-delivery .claude/skills/project-delivery && rm -rf skills-src

Use ~/.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/

Facts

Skill name
project-delivery
GitHub stars
2k
Token cost
~1.3k tokens
SKILL.md length
739 words
Files
2 (incl. references)
Skills in repo
178
Repo updated
First seen
Licence
MIT

At a glance

Plans and delivers a single project — scope, estimation, scheduling, critical path, tracking, and recovering when it slips.

  • SKILL.md covers Scope by exclusion, Estimate as a range, and say…, The critical path is where… and Track completion, not effort, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Project Delivery is an agent skill from cbrock84/headcount. Plans and delivers a single project — scope, estimation, scheduling, critical path, tracking, and recovering when it slips. Use this to plan a project, build or challenge a schedule, estimate credibly, track progress meaningfully, or recover a project that is late.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/sources.md`).

The repository describes itself as: An agent organization structured as a company — 15+ departments, 125+ skills, each independently installable, citing the standards and regulators that settle the question. Runs… The licence is MIT.

Example prompts

  • “Use the project-delivery skill to plan and delivers a single project — scope, estimation, scheduling, critical path, tracking, and recovering when…”
  • “/project-delivery”

What it can do on your machine

Read from SKILL.md and the folder at commit 98d1c17. 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

Project Delivery loads about 1.3k tokens when it runs, and up to ~1.7k if it reads all its reference files. Until then it costs about 71 tokens; SKILL.md has 739 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~71
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.7k

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 cbrock84/headcount at commit 98d1c17, republished under its MIT licence (© cbrock84). 739 words, ~1,254 tokens.

Download SKILL.mdSave it as .claude/skills/project-delivery/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
project-delivery
description
Plans and delivers a single project — scope, estimation, scheduling, critical path, tracking, and recovering when it slips. Use this to plan a project, build or challenge a schedule, estimate credibly, track progress meaningfully, or recover a project that is late.

Project delivery

A project is one bounded piece of work with an end. Coordinating several toward a shared outcome is pmo:program-management.

Scope by exclusion

Inclusions are agreed easily and understood differently. The exclusions do the work: what this project will not deliver, written down and acknowledged by the sponsor.

Unwritten exclusions return as assumptions, always late, always framed as something obviously included. Fixing that at the end is called scope creep; it is usually a documentation failure at the start.

Estimate as a range, and say what the range means

A single-point estimate is a forecast presented as a commitment. Give a range with the assumptions that would move it, and be explicit about confidence.

Estimate the work, not the desired date. Estimates negotiated downward do not change the work; they change when you find out, and the finding-out happens at the least recoverable moment.

Decompose until the pieces are comprehensible. Estimating a large unknown produces a number correlated with optimism rather than with the work.

The critical path is where attention belongs

Not everything late matters. Slippage on the critical path moves the end date; slippage elsewhere consumes float. Knowing which is which is the difference between useful concern and generalised anxiety.

Recalculate as things change — the critical path moves, and a team watching the original one is watching the wrong thing.

Hold buffer at the project level rather than padding each task. Padded tasks absorb their own buffer and deliver no earlier, because work expands and nobody reports finishing early.

Track completion, not effort

Percentage complete is self-reported optimism, and it famously stalls at 90%. Track binary completion of defined deliverables — done or not done, judged against a definition agreed in advance.

Watch the trend: whether the amount remaining is falling at the rate required. A project where remaining work is not decreasing is a project that is late, whatever the reported percentage.

Recovery

Diagnose first, since remedies do not overlap: scope larger than understood, capacity lower than planned, dependencies not delivering, or an estimate that was never realistic.

Then present options with consequences — cut scope and name what, extend and say by how much, or add capacity, which late in a project usually slows things further. Re-baseline once, visibly. Serial one-week slips destroy credibility far faster than a single honest reset.

Show full SKILL.md (355 more words)Show less

Change control is what makes the scope statement mean anything

A scope boundary that anyone can move in a conversation is not a boundary. Change control is the mechanism that turns it into one, and it needs to be light enough that people use it rather than route around it.

  • A change is anything that moves scope, date, or cost — including work that arrives described as a clarification. Most scope creep enters as a series of small reasonable requests, none of which was ever assessed against the whole.
  • Assess impact on all three before deciding. "Yes, and it adds two weeks" is a decision someone can make. "Yes" alone is how a plan quietly stops being achievable.
  • The person who can approve a change is the person who owns the consequence. If the sponsor approves scope but the team absorbs the date, changes will keep being approved.
  • Log rejected changes too. The record of what was declined is what stops the same request arriving three more times, and it is the honest answer when someone asks why a feature is missing.

Re-baseline when an approved change makes the old plan meaningless, and not otherwise. A baseline re-set to hide variance destroys the only reference you had.

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

Tooling

Delivery tracking: Jira, Asana, Linear, Monday.com, Smartsheet, Microsoft Project, and similar.

Portfolio and capacity: Jira Align, Planview, Adaptive Work, and similar. Worth it when you are reconciling many teams' plans against one capacity pool, not before.

The tool records the plan; it does not make the plan true. A status field nobody updates between meetings is worse than no field at all.

Never

  • Agree scope without written exclusions.
  • Present a single-point estimate as a commitment.
  • Report progress as percentage complete.
  • Add people to a late project and expect it to accelerate.

© cbrock84, MIT. 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 1 other file (references) in plugins/pmo/skills/project-delivery of cbrock84/headcount.

  • SKILL.md
  • references/sources.md

Open the folder on GitHubat commit 98d1c17

Compare with similar skills

Project Delivery 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.

Project Delivery compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Project Delivery this skillcbrock84/headcount2k—~1.3kAutomated safety check: PassMIT
Plancodewhale-hq/Codewhale41k—~213Automated safety check: PassMIT
Scheduleasgeirtj/system_prompts_leaks69k—~2.9kAutomated safety check: PassCC0-1.0
Scheduleasgeirtj/system_prompts_leaks69k—~597Automated safety check: PassCC0-1.0
Planningn8n-io/n8n207k—~2.5kAutomated safety check: PassCustom licence
Planasgeirtj/system_prompts_leaks69k—~5.1kAutomated safety check: PassCC0-1.0

Similar skills

  • Plan

    codewhale-hq/Codewhale

    Turn a sufficiently understood task into an ordered implementation plan with dependencies and verification.

    41k GitHub stars~213 tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Schedule

    asgeirtj/system_prompts_leaks

    Create, update, list, or run scheduled cloud agents (routines) that execute on a cron schedule.

    69k GitHub stars~2.9k tokensUpdated yesterday
    Productivity & AutomationAuto-check passed

  • Schedule

    asgeirtj/system_prompts_leaks

    Create or update a scheduled task that runs automatically. An agent skill from asgeirtj/system_prompts_leaks.

    69k GitHub stars~597 tokensUpdated yesterday
    Productivity & AutomationAuto-check passed

  • Planning

    n8n-io/n8n

    Official

    ONLY for coordinated multi-artifact work: multiple workflows with dependencies, shared data-table schema/migration across tasks, or the user explicitly asked to review a plan first.

    207k GitHub stars~2.5k tokensUpdated today
    Productivity & AutomationAuto-check passed

  • Plan

    asgeirtj/system_prompts_leaks

    On an explicit planning request, always call readskill for this skill before answering.

    69k GitHub stars~5.1k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Review Plan

    penpot/penpot

    Plan review flow — evaluate an implementation plan before it is executed, delegating the review to a subagent that follows the plan-review-criteria skill.

    61k GitHub stars~841 tokensUpdated today
    Agent WorkflowsAuto-check passed

More from cbrock84/headcount

All 178 skills in this repo

  • Agent Hierarchy

    cbrock84/headcount

    Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a…

    2k GitHub stars~1.2k tokensUpdated 22 days ago
    Auto-check passed

  • Access And Identity

    cbrock84/headcount

    Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process.

    2k GitHub stars~1.1k tokensUpdated 22 days ago
    Auto-check passed

  • Account Based Marketing

    cbrock84/headcount

    Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group…

    2k GitHub stars~1.2k tokensUpdated 22 days ago
    Auto-check passed

  • Activation

    cbrock84/headcount

    Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account.

    2k GitHub stars~865 tokensUpdated 22 days ago
    Auto-check passed

  • AI ML Governance

    cbrock84/headcount

    Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire.

    2k GitHub stars~1k tokensUpdated 22 days ago
    Auto-check passed

  • AI Research Analyst

    cbrock84/headcount

    Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit.

    2k GitHub stars~916 tokensUpdated 22 days ago
    Auto-check passed

Questions about Project Delivery

What does Project Delivery do?

Plans and delivers a single project — scope, estimation, scheduling, critical path, tracking, and recovering when it slips. Project Delivery is an agent skill from cbrock84/headcount. Plans and delivers a single project — scope, estimation, scheduling, critical path, tracking, and recovering when it slips.

How do I install Project Delivery in Claude Code?

Run `npx skills add cbrock84/headcount --skill project-delivery -a claude-code`. Or copy the skill folder (plugins/pmo/skills/project-delivery in cbrock84/headcount) into .claude/skills/project-delivery in your project. Claude Code loads it when a task matches its description.

How do I install Project Delivery in Codex?

Run `npx skills add cbrock84/headcount --skill project-delivery -a codex`. Or copy the skill folder (plugins/pmo/skills/project-delivery in cbrock84/headcount) into .agents/skills/project-delivery in your project. Codex loads it when a task matches its description.

Can I use Project Delivery 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 cbrock84/headcount --skill project-delivery -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-delivery, .gemini/skills/project-delivery, .github/skills/project-delivery and .opencode/skills/project-delivery in your project.

What does Project Delivery need to run?

SKILL.md names no scripts, command-line tools or credentials: Project Delivery is instructions for the agent only.

Does Project Delivery 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 Project Delivery 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 Delivery use?

Project Delivery 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 Project Delivery use?

About 1.3k tokens (SKILL.md is roughly 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 436 tokens, read only when the agent opens those files.

What are the alternatives to Project Delivery?

Skills that share tags, products or a category with Project Delivery: Plan (codewhale-hq/Codewhale, 41k stars), Schedule (asgeirtj/system_prompts_leaks, 69k stars), Schedule (asgeirtj/system_prompts_leaks, 69k stars) and Planning (n8n-io/n8n, 207k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Project Delivery?

cbrock84 (a GitHub user) maintains it in cbrock84/headcount, which has 2,016 GitHub stars. The repository holds 178 skills in this directory. The repository was last updated on September 17, 2026.

Source: cbrock84/headcount on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.