agentleFS
Sign inStart free
HybridAIOneHybridAIOne/hybridclaw/skills/project-manager/SKILL.md

project-manager

Skill159 starsChanged 30 days agoMITView on GitHub

Plan sprints, milestones, roadmaps, risks, dependencies, and stakeholder updates for team delivery.

35 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use boat-machines, controllers-policy and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Th0rgalSkill

    boat-machines

    When and how a mission should rent boat.dev managed VMs: whether to use one at all, size choice, one warm snapshot per project, forking the parent VM, sharing a VM between sequential siblings, stopping instead of idling, budgets and cleanup. Use before spawn_managed_machine, start_mission(remote_node_id=\"auto-managed:...\"), fork, snapshot or stop/resume tools.

    Also in 3 projects that use this

  • Th0rgalSkill

    controllers-policy

    Autonomy contract and routing index for autonomous project controllers. Loaded every tick; carries the rules that must survive cron-prompt rewrites.

    Also in 3 projects that use this

  • FlatbreadLabsSkill

    orchestrator-executor

    Coordinate large, long-running, parallel, architecture-sequenced, or isolated-worktree tasks with a cost-conscious orchestrator/executor model. Use when work needs a dependency graph, multiple agents, staged integration, durable asynchronous coordination, or independently reviewable changes.

    Also in 3 projects that use this

  • SashankMeka1Skill

    orchestrator-worker

    Use this skill when designing or building a multi-agent automation harness (e.g. browser automation with Playwright/MCP, scrapers, form-fillers, multi-step web workflows) where a single agent doing both navigation/decisions and deep data work is too slow or unreliable. Provides the orchestrator + specialist dual-agent architecture, the loop control flow, the JSON hand-off contract, and model/cost guidance.

    Also in 3 projects that use this

  • ClineSkill

    data-analyst

    Act as an interactive data analyst for ClickHouse-backed analytics. Use when the user asks questions about internal data, metrics, dashboards, telemetry, active users, revenue, funnels, trends, distributions, or wants an analyst-style conversation, ad hoc SQL, charts, or a data export against ClickHouse (local or ClickHouse Cloud).

    Also in 3 projects that use this

  • JeffallanSkill

    devops-engineer

    Creates Dockerfiles, configures CI/CD pipelines, writes Kubernetes manifests, and generates Terraform/Pulumi infrastructure templates. Handles deployment automation, GitOps configuration, incident response runbooks, and internal developer platform tooling. Use when setting up CI/CD pipelines, containerizing applications, managing infrastructure as code, deploying to Kubernetes clusters, configuring cloud platforms, automating releases, or responding to production incidents. Invoke for pipelines, Docker, Kubernetes, GitOps, Terraform, GitHub Actions, on-call, or platform engineering.

    Also in 3 projects that use this

  • +4 more from Th0rgal

The file

We split this skill into the rules it gives an agent

12 rules. 0 are common, 12 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 31 edited versions we read keep these.

  • 12

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill for delivery planning and team-facing coordination artifacts.

    line 20
  2. Distinctive:

    When the user does not specify a format, default to one of these:

    line 24
  3. Distinctive:

    Treat estimates as assumptions, not promises.

    line 55
  4. Distinctive:

    Prefer smaller deliverable increments over large all-at-once plans.

    line 58
  5. Distinctive:

    If dates are requested without capacity data, state the assumption clearly.

    line 59
  6. Distinctive:

    When the user asks for something pasteable into a team tool, keep formatting plain and compact.

    line 60
  7. Distinctive:

    Use a compact table or bullet list with:

    line 66
  8. Distinctive:

    Keep it short and decision-oriented:

    line 86
  9. Distinctive:

    Do not commit to deadlines without listing assumptions.

    line 96
  10. Distinctive:

    Do not hide dependencies in prose.

    line 97
  11. Distinctive:

    Do not confuse activity with progress.

    line 98
  12. Distinctive:

    Do not generate ceremony for its own sake when a lighter artifact will do.

    line 99

“Common” is measured: kept by at least 6 in 10 of the 31 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Project Management

Use this skill for delivery planning and team-facing coordination artifacts.

Core Outputs

When the user does not specify a format, default to one of these:

  • implementation plan
  • milestone table
  • risk register
  • stakeholder update
  • sprint plan
  • dependency map

Default Structure

For delivery planning, use:

  1. Goal
  2. Scope
  3. Milestones
  4. Risks and mitigations
  5. Dependencies
  6. Owners or recommended owners
  7. Next 3 concrete actions

For status updates, use:

  1. Overall status
  2. What moved this period
  3. Current blockers
  4. Decisions needed
  5. Next checkpoint

Working Rules

  • Treat estimates as assumptions, not promises.
  • Name the biggest risks early.
  • Sequence high-uncertainty work before polish work.
  • Prefer smaller deliverable increments over large all-at-once plans.
  • If dates are requested without capacity data, state the assumption clearly.
  • When the user asks for something pasteable into a team tool, keep formatting plain and compact.

Common Patterns

Risk Register

Use a compact table or bullet list with:

  • risk
  • impact
  • probability
  • mitigation
  • owner

Sprint Plan

Break work into:

  • sprint goal
  • committed items
  • stretch items
  • dependencies
  • explicit exit criteria

Stakeholder Update

Keep it short and decision-oriented:

  • objective
  • current state
  • what changed
  • risk or ask
  • next checkpoint

Pitfalls

  • Do not commit to deadlines without listing assumptions.
  • Do not hide dependencies in prose.
  • Do not confuse activity with progress; anchor on outcomes.
  • Do not generate ceremony for its own sake when a lighter artifact will do.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free