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

Schedule Development And Analysis

by cbrock84 in cbrock84/headcount

Builds and interrogates a project schedule — logic-driven sequencing, dependency types and lags, float and the critical path, resource loading and leveling, schedule risk analysis, and measuring…

MITAuto-check passed

Install Schedule Development And Analysis

skills CLI
$ npx skills add cbrock84/headcount --skill schedule-development-and-analysis -a claude-code

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

GitHub CLI
$ gh skill install cbrock84/headcount schedule-development-and-analysis --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/schedule-development-and-analysis .claude/skills/schedule-development-and-analysis && 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
schedule-development-and-analysis
GitHub stars
2k
Token cost
~1.3k tokens
SKILL.md length
737 words
Files
2 (incl. references)
Skills in repo
178
Repo updated
First seen
Licence
MIT

At a glance

Builds and interrogates a project schedule — logic-driven sequencing, dependency types and lags, float and the critical path, resource loading and leveling, schedule risk analysis, and measuring…

  • SKILL.md covers Build it from logic, not from…, Float is the information, and…, Load resources before you… and Analyze schedule risk rather…, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Schedule Development And Analysis is an agent skill from cbrock84/headcount. Builds and interrogates a project schedule — logic-driven sequencing, dependency types and lags, float and the critical path, resource loading and leveling, schedule risk analysis, and measuring progress against a baseline rather than against optimism. Use this to construct a schedule, audit one you have inherited, find out why a plan keeps slipping, work out what a date change actually costs, or judge whether a reported percentage complete means anything.

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 schedule-development-and-analysis skill to build and interrogates a project schedule — logic-driven sequencing, dependency types and lags…”
  • “/schedule-development-and-analysis”

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

Schedule Development And Analysis loads about 1.3k tokens when it runs, and up to ~1.5k if it reads all its reference files. Until then it costs about 124 tokens; SKILL.md has 737 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~124
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.5k

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). 737 words, ~1,250 tokens.

Download SKILL.mdSave it as .claude/skills/schedule-development-and-analysis/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
schedule-development-and-analysis
description
Builds and interrogates a project schedule — logic-driven sequencing, dependency types and lags, float and the critical path, resource loading and leveling, schedule risk analysis, and measuring progress against a baseline rather than against optimism. Use this to construct a schedule, audit one you have inherited, find out why a plan keeps slipping, work out what a date change actually costs, or judge whether a reported percentage complete means anything.

Schedule development and analysis

A schedule is a model of how work connects. Most schedules in circulation are a list of dates someone typed, which looks the same in a status deck and behaves completely differently when anything moves.

Build it from logic, not from dates

Every task except the first and last should be connected to something. A task with a date and no predecessor is an assertion; a task with a predecessor is a plan, because when the predecessor moves the task moves with it and the schedule tells you so.

  • Finish-to-start is the default and covers most real dependencies.
  • Start-to-start and finish-to-finish describe overlapping work honestly and are worth using rather than faking the overlap with an earlier date.
  • Lags should represent something real — curing time, a notice period, a review window. A lag used to make dates line up is a hidden assumption.

Hard-coded date constraints are where schedules go to die. Each one severs the logic at that point, so slippage upstream stops propagating and the schedule keeps reporting a date it can no longer support.

Float is the information, and the critical path is the consequence

Float is how long a task can slip before it moves the end date. The critical path is the chain with none. Attention belongs there and almost nowhere else — expediting work with three weeks of float buys nothing and consumes the same management capacity.

Two readings worth taking regularly: near-critical chains, which become critical after one bad week and are where surprises come from, and negative float, which means the schedule is already telling you the date is impossible and someone has not looked.

Load resources before you believe the dates

A schedule that assumes the same three people work on five parallel tasks is fiction that will resolve itself as a delay. Load the named constraint — the one team, the one approver, the one environment — and level it. Leveling extends the schedule; that extension was always there, it was just unrecorded.

Analyze schedule risk rather than adding a buffer at the end

Durations are ranges. Running the schedule with ranges rather than single durations shows something a buffer cannot: paths that merge. Where several chains converge on one milestone, the milestone waits for the latest of them, so the probability of hitting the date is far lower than the probability of any single chain hitting its own — which is why plans with many parallel workstreams slip even when no individual stream looks late.

A buffer at the end of the plan protects the end date. A buffer in front of each merge point protects the plan.

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

Measure progress against the baseline, not against effort

Keep a baseline and compare to it, or "we are 70% done" has nothing to be 70% of.

The useful comparison is three-way: what was planned to be complete by now, what is actually complete, and what it cost to get there. Those three answer different questions — the first two give you schedule performance, the last two give you cost performance, and a project can be ahead on one and badly behind on the other.

Percentage complete on in-progress work is where reporting rots. A task reported at 90% for three weeks is not 90% complete. Binary reporting — not started, in progress, done — with small enough tasks that "done" arrives often is more honest and takes less time to maintain.

Auditing a schedule you inherited

Look for these in order, because each one invalidates everything after it: tasks with no predecessor or successor, hard date constraints, negative float, durations longer than a reporting period, tasks that have been 90% complete for more than one period, and a baseline that has been re-set so often it no longer means anything.

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.

Never

  • Accept a date on a task with no logic behind it.
  • Hard-code a constraint to make a date hold. It stops the schedule from telling you the truth.
  • Report percentage complete on a task whose remaining work nobody has re-estimated.
  • Re-baseline to make variance disappear. Re-baseline when scope genuinely changed, and say which.

© 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/schedule-development-and-analysis of cbrock84/headcount.

  • SKILL.md
  • references/sources.md

Open the folder on GitHubat commit 98d1c17

Compare with similar skills

Schedule Development And Analysis 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.

Schedule Development And Analysis compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Schedule Development And Analysis this skillcbrock84/headcount2k—~1.3kAutomated safety check: PassMIT
Scheduleasgeirtj/system_prompts_leaks69k—~2.9kAutomated safety check: PassCC0-1.0
Scheduleasgeirtj/system_prompts_leaks69k—~597Automated safety check: PassCC0-1.0
Dependency Scanningsickn33/agentic-awesome-skills47k1 repos~2.4kAutomated safety check: PassMIT
Dependency Checkruvnet/ruflo74k—~258Automated safety check: PassMIT
Cron Scheduleruvnet/ruflo74k—~257Automated safety check: PassMIT

Similar skills

  • 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

  • Dependency Scanning

    sickn33/agentic-awesome-skills

    Scan package dependencies for known vulnerabilities using Snyk, Dependabot, and OWASP Dependency-Check.

    47k GitHub starsUsed in 1 repo~2.4k tokens
    SecurityAuto-check passed

  • Dependency Check

    ruvnet/ruflo

    Scan project dependencies for known vulnerabilities and CVEs.

    74k GitHub stars~258 tokensUpdated today
    SecurityAuto-check passed

  • Cron Schedule

    ruvnet/ruflo

    Schedule persistent background workers via CronCreate. An agent skill from ruvnet/ruflo.

    74k GitHub stars~257 tokensUpdated today
    Productivity & AutomationAuto-check passed

  • Scheduling

    asgeirtj/system_prompts_leaks

    Find meeting or appointment times, create private calendar holds or invitations, and reschedule or cancel events within the user's authorization.

    69k GitHub stars~1.4k tokensUpdated yesterday
    Auto-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 21 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 21 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 21 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 21 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 21 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 21 days ago
    Auto-check passed

Questions about Schedule Development And Analysis

What does Schedule Development And Analysis do?

Builds and interrogates a project schedule — logic-driven sequencing, dependency types and lags, float and the critical path, resource loading and leveling, schedule risk analysis, and measuring…. Schedule Development And Analysis is an agent skill from cbrock84/headcount. Builds and interrogates a project schedule — logic-driven sequencing, dependency types and lags, float and the critical path, resource loading and leveling, schedule risk analysis, and measuring progress against a baseline rather than against optimism.

How do I install Schedule Development And Analysis in Claude Code?

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

How do I install Schedule Development And Analysis in Codex?

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

Can I use Schedule Development And Analysis 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 schedule-development-and-analysis -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/schedule-development-and-analysis, .gemini/skills/schedule-development-and-analysis, .github/skills/schedule-development-and-analysis and .opencode/skills/schedule-development-and-analysis in your project.

What does Schedule Development And Analysis need to run?

SKILL.md names no scripts, command-line tools or credentials: Schedule Development And Analysis is instructions for the agent only.

Does Schedule Development And Analysis 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 Schedule Development And Analysis 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 Schedule Development And Analysis use?

Schedule Development And Analysis 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 Schedule Development And Analysis 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 246 tokens, read only when the agent opens those files.

What are the alternatives to Schedule Development And Analysis?

Skills that share tags, products or a category with Schedule Development And Analysis: Schedule (asgeirtj/system_prompts_leaks, 69k stars), Schedule (asgeirtj/system_prompts_leaks, 69k stars), Dependency Scanning (sickn33/agentic-awesome-skills, 47k stars) and Dependency Check (ruvnet/ruflo, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Schedule Development And Analysis?

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.