ui-implement
Story-to-code workflow for UI/front-end stories. Takes a Jira [UI] Story, plans the implementation using discovered design-system and testing conventions, writes contract-based unit tests and production code via TDD, validates against the project's CI expectations, and manages review via GitHub PRs. Use when implementing [UI] stories produced by the design workflow with a ui-design document. Activated by commands: /ingest, /plan, /revise, /code, /validate, /publish, /respond.
89%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
UI Implement Workflow Orchestrator
Quick Start
- If the user invoked a specific command (e.g.,
/plan,/code), read the matching file in commands/ and follow it. - Otherwise, read
skills/controller.mdto load the workflow controller:- If the user provided a Jira issue key or URL, execute the
/ingestphase - Otherwise, execute the first phase the user requests
- If the user provided a Jira issue key or URL, execute the
If a step fails or produces unexpected output (e.g., Jira MCP errors, test failures, build errors), stop and report the error to the user. Do not advance to the next phase. Offer to retry the failed step or escalate.
For principles, hard limits, safety, quality, and escalation rules, see guidelines.md.
- Repository
flightctl/ai-workflows
- Revision
b369da0
- Last updated
- First committed
Also appears in
since Oct 14, 2026
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.