Loading...
Loading...
Found 45 Skills
Amend architectural specifications through formal protocol.
Use when OpenSpec artifacts have been generated by /opsx:propose and need review before implementation begins — validates proposal scope, spec completeness, design decisions, and task executability
Use when creating or amending a Spec Kit project constitution, especially when `memory/constitution.md` is missing, contains `[PLACEHOLDER]` tokens, or principle changes must be propagated to planning/spec/task templates.
Conduct stakeholder analysis using identification, Power-Interest matrix classification, and influence strategy development. Use this skill when the user needs to map stakeholders for a project, manage conflicting interests, prioritize communication, or build a stakeholder engagement plan — even if they say 'who needs to approve this', 'how do I get buy-in', or 'who might block this project'.
Phase 1 of the Issue Workflow - Translate the user's problem into a reproducible, traceable {slug}-report.md through conversation. The AI only asks "what you saw, how to reproduce it, what should happen" here, and does not guess the root cause for the user (that's Phase 2's responsibility). This phase is also the only official decision point for determining whether to take the fast track or the standard path: first read the relevant code based on the user's description, and if the root cause can be identified at a glance and the changes required are minor, directly inform the user to take the fast track. Trigger scenarios: The user says "file an issue", "log this bug", "I found a problem". This is the starting point of the issue workflow with no pre-requisites.
Use when every architecture and implementation decision must be traceable with explicit rationale; pair with architect-stack-selector and addon-human-pr-review-gate.
Create stakeholder alignment artifacts including responsibility matrices, decision frameworks, and communication plans.
Phase 1 of the feature workflow — Draft a design document for the new feature, serving as the sole input for subsequent implementation and acceptance. First gather evidence (read architecture docs, review relevant code, grep to prevent term conflicts, check archives), then write a complete first draft in one go (including YAML frontmatter + three-tier structure + test design), submit it to the user for overall review, and iterate until approval. After approval, extract {slug}-checklist.yaml from {slug}-design.md for use in the next two phases. Trigger scenarios: "Start designing the solution", "Write design doc", "Prepare to implement XX", with the prerequisite that you already know what to do, who it's for, and how to define success.
Audit design documents for missing decisions, compatibility risks, rollout gaps, and observability omissions. Use whenever the user asks to review a design doc, architecture proposal, implementation-facing design, plan, or design-adjacent markdown file for completeness, migration strategy, rollback, data handling, or suggested additions without directly editing the document. Also trigger on short requests such as `review <file>.md` or `audit <file>.md` when the target looks like a design, plan, architecture, proposal, or decision document.
Use when you find additional work needed during task execution that's not in the original task description, to report it to ZŌE for review
Use when asked to review a plan, challenge a proposal, run a CEO review, poke holes in an approach, think bigger about scope, or decide whether to expand or reduce the plan.
Generate a requirements-quality checklist for an OpenSpec change and run it against the proposal/design/tasks/delta — validating completeness, clarity, consistency, and testability BEFORE you approve the spec. Modeled on GitHub Spec-Kit's /checklist. Use when reviewing a spec at the human approval gate, or before launching implementation, to catch under-specified requirements early.