project-manager
Skill0 starsChanged 2 months agoMITView on GitHub
Govern the complete project lifecycle from intake through design, development, QA, release, and closure using repository-owned artifacts, stage-aware gates, risks, and handoffs. Use when Codex needs to bootstrap feature or release records, review a PRD/UI design/technical design/test case/release record, audit cross-artifact consistency, run a lifecycle-stage gate, define role handoffs, or report milestone and artifact-readiness risks. Use project-structure-governance instead for document paths, naming, language, and repository archival rules.
38 other projects use a version of this.
Adopted by
Most recently taken up by
- teja1103/Claude-Skillstheir own version, first seen Nov 16, 2026
- coreyhaines31/makerskillstheir own version, first seen Nov 15, 2026
- sidekick0361/project-bootstrapstheir own version, first seen Nov 15, 2026
- Th0rgal/sandboxed.shtheir own version, first seen Nov 14, 2026
- Cure-Consulting-Group/ProductEngineeringSkillstheir own version, first seen Nov 12, 2026
- br3eze-code/br3eze-codetheir own version, first seen Nov 11, 2026
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.
Th0rgalSkillboat-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
Th0rgalSkillcontrollers-policy
Autonomy contract and routing index for autonomous project controllers. Uses a controller mission and text board.
Also in 3 projects that use this
FlatbreadLabsSkillorchestrator-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
SashankMeka1Skillorchestrator-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
JohnJBorenSkillproduct-manager
Product development workflows, PRDs, prioritization frameworks, and roadmap planning
Also in 4 projects that use this
ClineSkilldata-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
- +4 more from Th0rgal
Other versions38 projects use a version of this.
Word for word · 1
- farfarfun-skill/project-manager★ 0100% same
Edited · 0
None found.
Wrote their own version · 37
- coreyhaines31/makerskills★ 916same name
- Th0rgal/openagent★ 717same name
- Th0rgal/orb★ 717same name
- Th0rgal/sandboxed.sh★ 717same name
- pwrdrvr/openclaw-codex-app-server★ 265same name
- HybridAIOne/hybridclaw★ 162same name
- tronghieu/agent-skills★ 94same name
- pwrdrvr/ghcrawl★ 78same name
- OpenCoven/coven★ 75same name
- nahisaho/MUSUBI★ 74same name
27 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository2 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 4 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 33 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill as the complete project-lifecycle governance entrypoint.
- Distinctive: line 12
Use one explicit stage for every consolidated gate:
- Very specific: line 50
Use $project-structure-governance before creating or auditing lifecycle artifacts.
- Distinctive: line 57
Run commands from this skill's repository root.
- Very specific: line 75
Use --format json when another tool consumes a checker result.
- Distinctive: line 91
Do not claim business correctness from structural checks.
“Common” is measured: kept by at least 6 in 10 of the 33 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.
Files
Project Manager
Use this skill as the complete project-lifecycle governance entrypoint. Judge artifact readiness and traceability; do not replace product, engineering, QA, or release owners' final decisions.
Select The Lifecycle Stage
Use one explicit stage for every consolidated gate:
| Stage | Required outcome |
intake | PRD is ready for downstream design |
design | PRD and local UI handoff are ready |
development | Technical contract, schema, owners, and test design are ready for implementation |
qa | Development inputs remain consistent and test execution can proceed |
release | Test evidence is present; run the event-scoped release gate separately |
closure | Release is complete and retrospective evidence is archived |
Route The Request
Inspect the supplied artifact path and requested outcome, then select the narrowest module:
| Request or artifact | Module | Read before use |
| Initialize or audit project document paths and language | $project-structure-governance | Use that skill's canonical layout |
| Review or fix a repository's README structure, or its GitHub description/Topics | $github-repo-standards | Use that skill's GitHub repo standard |
| Create a new feature documentation skeleton | feature-doc-bootstrap | New Demand Checklist |
| Create an event-scoped release record | release-record-bootstrap | Release Template |
Review docs/product/<feature>/ | prd-qa-checker | PRD QA Rules |
Review docs/design/<feature>/ and local design assets | ui-design-checker | UI Design Rules |
Review docs/development/<feature>/ | architecture-design-checker | Architecture Rules |
Validate docs/development/<feature>/openapi/001-openapi.yaml | api-contract-checker | API Contract Rules |
Review docs/testing/<feature>/test-cases/ | test-case-checker | Test Case Rules |
Review docs/testing/<feature>/test-report/ | test-report-checker | Test Report Rules |
Review docs/retrospective/<feature>/ | retrospective-checker | Retrospective Rules |
| Review milestones and risks | project-status-checker | Project Status Rules |
| Audit one feature across all artifacts | artifact-consistency-checker | Consistency Rules |
| Run the complete feature gate | feature-governance-check | Governance Rules |
Review docs/release/<release-event>/ | release-readiness-checker | Release Rules |
| Define lifecycle workflow, roles, or handoffs | project-development-standard | Development Standard |
For a generic project-management check, inspect available documents first. Do not guess the module from the request wording alone. For API contract or design-to-implementation diff requests, apply the manual development standard; dedicated automated modules do not exist yet.
Delegate Document Governance
Use $project-structure-governance before creating or auditing lifecycle artifacts. Treat its references/project-layout.json as the only authoritative path definition and its checker result as the document-storage gate. Do not redefine the complete directory layout in this skill.
Apply its total-part document bundle standard: start every bundle with 001-overview.md, keep one topic per numbered file, and use continuous three-digit numbering.
Before creating a feature artifact, search its canonical path returned by the structure-governance skill. Update an existing feature bundle and append numbered chapters or change records for enhancements or fixes instead of creating a parallel bundle. Continue to treat shared project state as non-overwritable during feature initialization.
Run Modules
Run commands from this skill's repository root. Replace paths and identifiers with the target workspace values.
python3 scripts/feature_doc_bootstrap.py --workspace /path/to/repo --feature payment-confirmation --issue WAR-342
python3 scripts/release_record_bootstrap.py --workspace /path/to/repo --date 2026-07-12 --issue WAR-346 --slug payment-release
python3 scripts/prd_qa_checker.py --prd docs/product/payment-confirmation/ --issue WAR-342 --output auto
python3 scripts/ui_design_checker.py --ui docs/design/payment-confirmation/ --issue WAR-342 --output auto
python3 scripts/architecture_design_checker.py --design docs/development/payment-confirmation/ --issue WAR-342 --output auto
python3 scripts/api_contract_checker.py --input docs/development/payment-confirmation/openapi/001-openapi.yaml --baseline previous-openapi.yaml --fail-on block
python3 scripts/test_case_checker.py --testcase docs/testing/payment-confirmation/test-cases/ --issue WAR-342 --output auto
python3 scripts/artifact_consistency_checker.py --workspace /path/to/repo --feature payment-confirmation --stage development --issue WAR-342 --output auto
python3 scripts/feature_governance_check.py --workspace /path/to/repo --feature payment-confirmation --stage development --issue WAR-342 --output auto
python3 scripts/release_readiness_checker.py --release docs/release/2026-07-12-WAR-346-payment-release/ --issue WAR-346 --output auto
python3 scripts/test_report_checker.py --input docs/testing/payment-confirmation/test-report/
python3 scripts/retrospective_checker.py --input docs/retrospective/payment-confirmation/
python3 scripts/project_status_checker.py --input docs/project/project-status.yamlUse --format json when another tool consumes a checker result. For CI feature gates, pass --fail-on revise or --fail-on block to feature-governance-check; it returns exit code 1 when the final decision reaches the selected threshold.
The standalone lifecycle checkers support the same --fail-on thresholds. Use api-contract-checker --baseline when a previous contract is available to detect removed operations.
Apply The Output Contract
Return:
- module-specific decision
- normalized decision:
allow,revise, orblock - risk:
low,medium, orhigh - passed checks
- missing or weak items with concrete repair actions
- a paste-ready issue comment when requested
Aggregate multiple modules using the strictest decision and highest risk. Save durable generated reports under docs/review/... and cite that path in issue comments.
Do not claim business correctness from structural checks. If an input diverges heavily from its template, state that coverage is partial and lower confidence. Do not invent missing requirements. Final release approval remains with the accountable release owner even when the checker returns allow.
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
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.

