📦
human-docs
81Create Human-Ready AI Documentation
Detailed AI context files are often too long for quick human review. This skill turns them into summaries, quick starts, and Mermaid visual guides.
Documentation View
Skills main-orchestrator
📦
main-orchestrator
Content revision r1 Safe ⚙️ External commands
Coordinate Multi-Domain Engineering Work
Complex feature requests often stall when teams miss dependencies across frontend, backend, data, testing, and DevOps. This skill converts requirements into coordinated epics, task assignments, success criteria, and progress tracking.
Supports: Claude Codex Code(CC)
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "main-orchestrator" from https://skillstore.io/skills/brownbull-main-orchestrator.md and its manifest at https://skillstore.io/api/skills/brownbull-main-orchestrator/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "main-orchestrator". Add OAuth2 login with Google and GitHub.
Expected outcome:
The skill produces a high-priority authentication epic with separate UI, API, database, and end-to-end test tasks, plus dependencies and validation goals.
Using "main-orchestrator". The frontend needs an endpoint that backend has not built.
Expected outcome:
The skill recommends a mock API task, a backend contract task, an explicit dependency, and a logged architecture decision.
Using "main-orchestrator". Several critical tasks compete for limited execution capacity.
Expected outcome:
The skill orders tasks by business impact, records delay reasoning, communicates priority, and updates timeline estimates.
Security Audit
Safev8 • 7/6/2026 Open versioned report
The static analyzer flagged Markdown code fences and inline file path formatting as Ruby or shell backtick execution. Review of SKILL.md found planning templates, task routing guidance, and repository state file references, but no executable shell commands or prompt injection attempts.
1
Files scanned
289
Lines analyzed
0
Review items
0
False positives ignored
Risk Factors
⚙️ External commands (21)
SKILL.md:35-45 SKILL.md:45-51 SKILL.md:51-72 SKILL.md:72-86 SKILL.md:86-87 SKILL.md:87-95 SKILL.md:95-96 SKILL.md:96-97 SKILL.md:97-98 SKILL.md:98-102 SKILL.md:102-103 SKILL.md:103-104 SKILL.md:104-110 SKILL.md:110-116 SKILL.md:116-120 SKILL.md:120-129 SKILL.md:129-163 SKILL.md:163-198 SKILL.md:198-200 SKILL.md:200-204 SKILL.md:204-237
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/brownbull-main-orchestrator/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/brownbull-main-orchestrator?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/brownbull-main-orchestrator?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/brownbull-main-orchestrator/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/brownbull-main-orchestrator.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
Brownbull. (2026). main-orchestrator security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/brownbull-main-orchestrator/audits/8BibTeX citation
@techreport{brownbull-brownbull-main-orchestrator-2026,
author = {Brownbull},
title = {main-orchestrator security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/brownbull-main-orchestrator/audits/8},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "main-orchestrator security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
- name: "Brownbull"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/brownbull-main-orchestrator/audits/8"
identifiers:
- type: other
value: "skillstore:brownbull-main-orchestrator:audit:8"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: High 55
Architecture
85
Maintainability
87
Content
70
Community
83
Spec Compliance
What You Can Build
Plan a Cross-Functional Feature
Convert a broad feature request into scoped tasks for UI, API, data, testing, and deployment work.
Coordinate Engineering Dependencies
Identify task order, blocking relationships, and shared contracts before implementation starts.
Recover a Stalled Epic
Review task state, resolve ownership conflicts, and re-sequence work across specialized orchestrators.
Try These Prompts
Break Down a Feature
Use the main-orchestrator skill to break this feature into an epic, domain tasks, dependencies, and success criteria: [feature request].
Assign Work by Domain
Review this requirement and assign tasks to frontend, backend, data, test, and DevOps orchestrators. Include task goals and validation checks.
Resolve Dependencies
Analyze this epic for cross-domain conflicts, circular dependencies, missing contracts, and sequencing problems. Recommend a revised task order.
Manage an Epic Lifecycle
Create an execution plan for this PRD. Include epic structure, domain tasks, risk controls, progress events, quality gates, and documentation triggers.
Best Practices
- Provide a clear requirement, target domains, success criteria, and known constraints before decomposition.
- Keep each generated task owned by one domain orchestrator with explicit dependencies.
- Review task validation checks before implementation starts, especially security and failure cases.
Avoid
- Do not create large tasks that span several domains without clear ownership.
- Do not skip test requirements or quality gates to accelerate delivery.
- Do not bypass task logs, state files, or decision records during coordination.
Frequently Asked Questions
What does this skill coordinate?
It coordinates product requirements, epics, domain tasks, dependencies, quality checks, progress events, and documentation triggers.
Does it write production code?
No. It plans and routes work to specialized orchestrator skills that handle domain-specific implementation.
Which tools can use this skill?
The report marks it as compatible with Claude, Codex, and Claude Code.
Does it require other skills?
It is designed to work with frontend, backend, data, test, DevOps, and human documentation orchestrator skills.
Can it handle single-domain requests?
Yes, but the skill recommends direct delegation when one specialist orchestrator can complete the work alone.
What project files does it reference?
It references task state files, decision records, standards documents, and an operations log for coordination context.
Developer Details
Author
BrownbullLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
dd4a3ef9f20ddf38830950b4bb713df96b431fd6
Maintenance freshness
7/18/2026
Usage
8 downloads · 225 views
File structure
📄 SKILL.md
More from Brownbull
View all📦
devops-orchestrator
79Coordinate DevOps Delivery
DevOps work often spans pipelines, infrastructure, monitoring, and deployment decisions. This skill organizes those tasks into checklists, handoffs, and rollout plans.
DevOps & Infrastructure View
📦
human-docs-generator
79Generate Role-Based Human Documentation
Technical changes are hard for different teams to understand quickly. This skill turns project context into short role-based guides with examples, diagrams, and checks.
Documentation View
📦
data-orchestrator
79Coordinate Data Pipelines and Quality Checks
Data pipeline work can become inconsistent when ingestion, features, quality, and reporting are planned separately. This skill organizes data tasks around pipeline context, quality gates, lineage, and handoffs.
Data & Analytics View
📦
test-orchestrator
79Coordinate Testing Across Your Project
Test planning can drift when teams manage test types separately. This skill organizes coverage goals, quality gates, execution flow, and reporting.
Coding & Development View
📦
frontend-orchestrator
78Coordinate Frontend Delivery
Frontend tasks often span components, state, routes, tests, and documentation. This skill organizes that work into clear context packages and quality checks.
Coding & Development View
Related Skills
View all📦
feature-file
80Track Feature Requirements in YAML
by Chemiseblanc
Teams lose project intent when requirements live only in chat or task lists. This skill keeps scope, tests, decisions, and progress in a persistent features.yml file.
Productivity View
📦
interactive-planner
80Plan Requirements with Interactive Questions
by DNYoussef
Ambiguous project requests often lead to missing requirements and rework. This skill guides Claude, Codex, and Claude Code through structured question batches.
Productivity View
📦
brainstorming
79Plan Creative Work Before Building
by ZhanlinCui
Teams often start implementation before goals, constraints, and trade-offs are clear. This skill guides Claude, Codex, and Claude Code through structured brainstorming before design work begins.
Productivity View
📦
grilling
79Stress-Test Your Plan Before Building
by mattpocock
Unresolved decisions can make a plan expensive to change during implementation. This skill interviews you systematically and recommends an answer for each decision.
Productivity View
📦
version-planner
79Plan Product Versions
by yunshu0909
Product ideas often grow too large before teams know what to build first. This skill turns requirements into a staged MVP and version roadmap with clear validation points.
Productivity View
📦
task-planning
79Plan Agile Tasks and User Stories
by supercent-io
Teams often receive broad feature requests without clear tasks, priorities, or acceptance criteria. This skill turns feature ideas into user stories, sprint backlog items, dependencies, and Definition of Done checks.
Productivity View