technical-project-orchestrator
Skill0 starsChanged 25 days agoMITView on GitHub
Coordinate multi-stage product delivery from agreed requirements to PRs and releases with critical paths, scoped Codex tasks and evidence-based status.
In this repository28 other files it gives its agents.
- agent-skill-security-auditorSkill
- backend-api-engineerSkill
- backend-debuggingSkill
- backup-disaster-recoverySkill
- code-review-prSkill
- database-transaction-integritySkill
- dependency-supply-chain-auditorSkill
- devops-ci-cdSkill
- documentation-handoverSkill
- frontend-design-directionSkill
- llm-api-integrationSkill
- load-resilience-testingSkill
- mcp-integration-builderSkill
- observability-monitoringSkill
- performance-accessibilitySkill
- playwright-webapp-testingSkill
- privacy-data-governanceSkill
- product-business-analystSkill
- project-bootstrap-environmentsSkill
- qa-release-gatekeeperSkill
- qa-test-strategySkill
- react-artifacts-builderSkill
- security-authorization-auditorSkill
- skill-authoring-toolkitSkill
- skill-evaluation-benchmarkSkill
- software-architectSkill
- theme-design-systemSkill
- visual-assets-designSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
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
- Distinctive: line 7
Read task context, live repository issues/PRs and established ADRs.
- Distinctive: line 16
Do not invent work progress or substitute planning for execution.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Technical project orchestration
- Read task context, live repository issues/PRs and established ADRs. Keep confirmed facts distinct from remembered plans.
- Define outcome, non-scope, acceptance gates, constraints, available owners and release environment.
- Build a dependency graph from product scope to design, data, backend, frontend, QA, deployment and operations; minimize circular handoffs.
- Split work into small executable tasks with IDs, paths, inputs, deliverables, dependencies, review owner and clear stop conditions.
- Trigger companion skills only for material issues: architecture, DB integrity, security, UX, testing, deployment, observability.
- Track status as PLANNED, READY, IN PROGRESS, BLOCKED, TESTED, RELEASED or DONE, with evidence. Code merged is not synonymous with deployed.
- Protect ongoing user work: no unapproved destructive cleanup, environment changes, production writes or spurious repo cloning.
Output: critical path, task queue, dependency blockers, acceptance gates, evidence references and next actions. Do not invent work progress or substitute planning for execution.
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.