Agent skill · operations · aiskillstore
managing-workflow
Manages the specification-driven development workflow. Use this skill when the user runs /orbit, requests to "define feature", "create plan", "implement", or needs workflow guidance. It detects the current phase from artifacts and executes the appropriate action.
Why this skill is useful
Adds executable scripts for managing specification-driven development workflows that automate phase transitions and validation checks.
What it needs
Requires bash, jq installed locally. About 7k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Orbit Workflow Single skill for specification-driven development. Artifacts are the source of truth. Initialization <context-loading> Before any workflow action, load full context with a single Bash call: This returns JSON with: suggestion: Recommended next action current: Active feature state and artifacts features.active: All features with frontmatter state features.inprogress: Features needing attention architecturefiles: Available architecture docs Use this context for all decisions. Avoid additional Read calls for state detection. </context-loading> Phase Detection Phase is stored in spec.md frontmatter status field: Status Artifacts Next Action -------- ----------- ------------- initialize None Create spec.md specification spec.md (no [CLARIFY]) Create plan.md clarification spec.md with [CLARIFY] Resolve questions planning spec.md + plan.md Create tasks.md implementation tasks.md has - [ ] Execute tasks complete All tasks - [x] Archive or new feature Frontmatter Schema spec.md Frontmatter Updating Frontmatter On every phase transition, use the skill's built-in scripts: Or with Edit tool - update the status line in frontmatter. Phase Gates (MANDATORY) You MUST validate before ANY phase transition. This is NOT optional. Phase Prerequisites Target Phase Required Artifacts If Missing -------------- ------------------- ------------ specification None - clarification spec.md Create spec first planning spec.md (no [CLARIFY]) Resolve clarifications implementation spec.md, plan.md, tasks.md Create missing artifacts complete All tasks [x] Complete remaining tasks Enforcement Rules 1. NEVER skip directly to implementation - plan.md and tasks.md MUST exist 2. NEVER mark complete with unchecked tasks - all [ ] must be [x] 3. If validation fails: Create the missing artifact, don't proceed 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/managing-workflow