--- name: workflow description: Orchestrate repository requests using relevant context, focused skills, implementation, and verification. --- # Workflow Skill ## Workflow 1. **Establish context:** Use `get-context` to read relevant specifications. If `/context` is missing, recommend `onboard-repository`; if declined, stop before implementation. 2. **Clarify:** Ask concise questions about blocking ambiguity. State non-blocking assumptions and keep open questions visible. 3. **Plan:** Scale the plan to the task; seek feedback before substantial, risky, or materially ambiguous work. 4. **Update context:** Before non-context-neutral implementation, use the relevant `context-*` and `document-context` skills to update the specification with intent and acceptance needs, not implementation details. Resolve blockers first. Context-neutral changes preserve all documented expectations (for example, formatting or refactoring); when in doubt, treat a change as non-neutral and state any neutral assumption in the summary. 5. **Implement:** Delegate to `make-change` after the context update. Follow any repository-specific approval policy and implement only documented or context-neutral changes. 6. **Document and verify:** Review user-facing documentation; update it when behavior or usage changes. Run relevant checks and report results, skipped checks, and limitations. A context validator alone does not verify behavior. 7. **Review:** Summarize the outcome and remaining risks. Consider `maintain-context` when the repository specifications may be stale. ## Exceptions - For focused requests, inspect only relevant context areas and dependencies. - Stop if relevant context is missing or contradictory; proceed with explicit assumptions only for non-blocking gaps.