- Home
- Skills
- Jcastillotx
- Vibe Skeleton App
- Orchestrate
orchestrate_skill
- JavaScript
0
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill jcastillotx/vibe-skeleton-app --skill orchestrate- SKILL.md5.7 KB
Overview
This skill manages a 12-phase development lifecycle and enforces quality gates to keep projects on track. It helps start new projects, advance phases only when criteria are met, and navigate directly to any phase while recording context and session logs. Use it to formalize handoffs, required artifacts, and responsible agents for each stage.
How this skill works
The skill stores project context and phase state in a central active context file and validates phase-specific quality gates before permitting transitions. Commands start a new project, move to the next phase with gate checks, jump to a named phase after validating intermediate gates, and show current status including gate outcomes and active tasks. On every successful transition it updates the context with timestamps, primary agent, and a session log entry.
When to use it
- Initialize a new application project and capture required identity fields
- Advance the lifecycle only when deliverables and gates are satisfied
- Jump directly to a later phase when all intermediate gates are already met
- Check the current phase, assigned agent, and gate status for audits or planning
- Enforce coding standards and compliance before testing and release
Best practices
- Answer all Project Identity questions when creating a project to avoid blocked gates
- Keep CLAUDE-activeContext.md current: phase, artifacts, and session logs enable accurate validations
- Attach clear evidence for each gate (docs, PRs, tests) so the skill can validate automatically
- Run standards and code compliance checks early in development to reduce rework
- When a gate fails, follow the suggested remediation steps before retrying advancement
Example use cases
- /orchestrate new-project to collect application name, owner, license, and contact before work begins
- /orchestrate next-phase after sprint completion to verify code, tests, and standards are met
- /orchestrate requirements to jump to the Requirements phase when user stories are already documented
- /orchestrate status before planning meetings to report phase, primary agent, and pending gate items
- Use the skill to enforce security and review gates (Security Audit, Code Review) before deployment
FAQ
The skill will create the active context file and initialize the project at Phase -1 (Project Identity).
Can I jump to a target phase if intermediate gates are incomplete?
No. The skill validates all gates between the current and target phase and reports any failures with actionable remediation suggestions.