outcome-translator
Outcome Translator Skill
Purpose: Non-technical founders speak in outcomes. Engineers speak in tasks. This skill bridges the gap — translating every outcome phrase into a provable engineering plan.
Locale: en-AU — colour, behaviour, optimisation, organised, licence (noun).
When to Invoke
Invoke this skill BEFORE any action when the user's message contains:
- Completion claims: "finished", "done", "complete", "ready"
- Launch instructions: "launch it", "ship it", "go live", "release it", "deploy"
- Goal statements: "make it work", "just fix it", "get it working"
- Readiness claims: "production ready", "ready for clients", "ready to sell"
More from cleanexpo/unite-hub
tdd
Use when implementing any feature or bug fix. Hard gate — no production code without a failing test first. Applies to vitest (apps/web/) and pytest (apps/backend/). Triggers on "implement", "add feature", "fix bug", "new component", "new endpoint", or any code-writing task.
1idea-to-production
Plain-English pipeline from idea to production — routes user requests to the right phase and agent
1oauth-flow
OAuth 2.0 and OIDC integration with PKCE, Supabase Auth providers, and redirect URI validation
1health-check
>-
1csv-processor
>-
1vector-search
>-
1