Menu
Captures optional UI and UX flows, screen-level requirements, and interaction notes before implementation.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Bootstraps `.skills/planning.json`, `.skills/execution.json`, and `.skills/conventions.json` for a repository, and can also scaffold a wiki knowledge layer next to the planning feature directory. Use when a user asks to configure a project, initialize `sirius-skills` settings, apply generic defaults, add Jira-oriented conventions, or bootstrap the repo's wiki skeleton.
Canonical workflow for creating and managing durable subfeatures under an existing feature. Use this whenever the user asks to add, create, start, open, or bootstrap a subfeature so downstream planning skills keep the expected metadata and discovery-draft lifecycle.
Reconcile one planning target, optionally execute planning owners in sequence, and persist checkpointed resume context through approval, optional auto-commit handoff, and planning-commit handoff.
Converts repo stories and planning docs into directly executable, dependency-aware work items with traceability and execution handoff.
Closes the active execution slice with validation and records durable closure metadata while invoking shared owner-completion reconciliation.
Produces feature-level system-design.md artifacts before breakdown when a feature needs architecture, interface, constraint, failure-handling, or validation decisions captured durably.
| name | ui-flow |
| description | Captures optional UI and UX flows, screen-level requirements, and interaction notes before implementation. |
Use this skill when a project needs screen flows, interaction requirements, or UX notes before implementation work is decomposed.
<feature_path>/ui-design.mdOptional companion output:
<feature_path>/user-stories.mdResolve <feature_path> as <planning_dir>/<feature-slug>/.
.skills/planning.json defines planning_dir, use that as <planning_dir>.docs/features.discover.md and system-design.md when present.ui-design.md with screen-level requirements and edge cases.sirius manage-planning sync-status <feature-selector> --through design_ready when the feature requires UI flow so metadata catches up once the design packet is complete.breakdown.