simonasrazm

Starts and manages SFLO factory runs through the configured runner. Use when the user explicitly asks to start, run, resume, list, kill, clean, or inspect an SFLO factory, including requests to build something with SFLO. Do not use when `SFLO` or `SFLO:` appears only in quoted text, documentation, examples, code, logs, or vulnerability discussion.

Build products using the SFLO pipeline — a gated PM→Dev→QA process with configurable gates, threshold, and guardian safety. Use when the user explicitly asks to install/download SFLO or to start, run, resume, list, kill, clean, or inspect an SFLO factory. Do not use for quoted SFLO text, docs, logs, or vulnerability discussion.

Starts and manages SFLO factory runs through the configured runner. Use when the user explicitly invokes `/sflo` to start, run, resume, list, kill, clean, or inspect an SFLO factory. Do not use when `SFLO` or `SFLO:` appears only in quoted text, documentation, examples, code, logs, or vulnerability discussion.

Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

Build products using the SFLO pipeline — a gated PM→Dev→QA process. Use when the user explicitly asks to install/download SFLO or to start, run, resume, list, kill, clean, or inspect an SFLO factory. Do not use for quoted SFLO text, docs, logs, or vulnerability discussion.

Zero-shot enhancer. Use when the user invokes smart-shot or asks very ambiguos and short prompt

Evidence-first STR (Simon Troubleshoot) diagnostic workflow for human-triggered troubleshooting. Use when the user says "STR:" or asks to diagnose what is wrong, find a root cause, challenge assumptions, or produce a data-driven troubleshooting report using isolated Troubleshooter and Interrogator roles. Requires two independent role contexts; refuse rather than simulate both roles in one shared context.