skills/brief-to-live/SKILL.md
--- name: brief-to-live description: Take a brief/spec/task handed over in an interview or customer engagement and drive it end-to-end — grill + research → ingest to an LLM wiki vault → baseline infra → GitHub parent issues → auto-slice → autonomous build (ultracode) → a business/tech/way-of-working presentation. It's a conductor that chains existing ronan skills with human-in-the-loop checkpoints. Triggers when Ronan says he's been given a spec/brief/task to plan or implement — and SPECIFICALLY
npx skillsauth add RonanCodes/ronan-skills skills/brief-to-liveInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
The front door for "someone handed me a brief, take it all the way to shipped + presented." This skill is a conductor — it sequences existing ronan skills and owns the human-in-the-loop checkpoints. It does NOT reimplement grill/research/slice/build logic.
Status: scaffold. Phases 1-3 are the priority to flesh out first (the planning half). Phases 6-9 reuse mature skills and need mostly glue + checkpoint logic.
Ronan was given a brief/spec/task (interview, customer engagement, stakeholder) and
needs to plan and/or implement it. Explicit housapp trigger: "I got the housapp
brief / task and need to implement it" → run this flow against the housapp repo and
reuse the housapp wiki vault.
Run phases in order. Phases 2→3 end in a natural PAUSE (Ronan goes off to do ChatGPT
deep research + Mobbin design); resume at phase 5 when material is pasted back.
Use --phase <n> / --resume to re-enter mid-flow.
/ro:grill-with-docs/ro:wiki + ro:wiki-curatorhousapp vault
(~/Dev/ai-projects/llm-wiki/vaults/llm-wiki-housapp/). If unsure, ask.ro:wiki-curator agent
(single-writer librarian; keeps main context clean).mcp__mobbin assistance./ro:new-app (or the existing repo if implementing into one), /ro:supabase,
/ro:domain / /ro:cloudflare-dns. Fresh project + subdomain each engagement./ro:write-a-prd / /ro:generate-spec/ro:slice-into-issuesready-for-agent)./ro:ultracode/ro:create-crm as the domain
generator (umbrella + component relationship).interview-build-session / housapp-build-session / /ro:build-session-deckronan-private-skills/housapp-build-session./ro:video-summarize it (transcript + summary + scene
screenshots) → ingest the synthesis. Never just link it.ro:wiki-curator into the engagement's vault./ro:create-crm — a domain generator this skill's build phase calls for CRM briefs./ro:ultracode — the build engine (phase 8)./ro:grill-with-docs, deep-research, /ro:wiki, /ro:slice-into-issues,
interview-build-session — the chained phase skills.--resume across the phase-3 pause./ro:pushover + /ro:telegram + completion
report at the end, per the local-factory rule).testing
--- name: linear-pipeline description: The Fable orchestrator for a single dispatched Linear ticket. Holds almost no context itself; it receives `--issue <ID> --detached`, decides the stage sequence, and fans out a sub-agent per stage, passing forward only each stage's artifact (never re-derived, never inlined into its own context). Step zero, before any planning or stage routing, is a boundary triage against `canon/security-boundary.md` (#199): a match tags Ronan Connolly and stops the run, no
development
--- name: in-your-face description: Capture a chat-only answer into a durable artifact (markdown + HTML, PDF when cheap) and launch it automatically so the user cannot miss it. Use when user says "in your face", "don't let me lose this", "save that answer", "make that durable", or right after answering a substantive side question (a recipe, comparison, how-to, or generated prompt) that would otherwise die with the context. category: workflow argument-hint: [--no-open] [--vault <short>] [hint of
tools
One-shot headless OpenAI Codex CLI calls for background/admin AI tasks — summaries, classification, extraction, admin glue. The default engine for anything that runs AI constantly in the background (daemon-driven, per-event), because it bills the flat ChatGPT subscription instead of Claude usage or per-token API spend, and it keeps working while Claude is rate-limited. NEVER for coding — coding stays Claude. Use when a skill or daemon needs a cheap always-on AI call, when the user says "use codex", "ask codex", "codex as backup", or when building a background summarizer/classifier into a listener or loop. Reads auth from ~/.codex/auth.json (ChatGPT account, no API key).
research
Turn a warranty rejection, repair quote, or RMA email into a cited decision brief — legal read (NL/EU consumer law), is the part user-serviceable, live part and new-unit prices, repair-vs-DIY-vs-new economics, before-you-send-it checklist, deadlines. Use when the user pastes or screenshots a repair quote, warranty rejection, "not covered" email, onderzoekskosten fee, or asks "should I repair or replace this".