← fstackCONTENT HISTORY

Update to fstack

Snapshot Sep 30, 2026 · 23:16 UTC · version 1.1.2

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Master orchestrator for fstack. Routes founder operations (sales, support, social, strategy) and engineering work through /engineer-mode. Use for /fstack, /fabio-mode, or founder/engineering requests.",
  "included_files": [],
  "name": "fstack",
  "skill_md_contents": "---\nname: fstack\ndescription: Master orchestrator for fstack. Routes founder operations (sales, support, social, strategy) and engineering work through /engineer-mode. Use for /fstack, /fabio-mode, or founder/engineering requests.\nmenu-description: master entry point for founder operations and engineering rigor\n---\n\n# fstack (Fabio's Stack / Founder's Stack)\n\n> \"throughput without quality is not a goal i aspire to. if you want to go fast, go deep first.\"\n> Lauren Tan (poteto)\n>\n> \"Talk to users. Build the thing. Don't ship slop. Be a decent human.\"\n> Fabio Parlascino\n\n`fstack` is a harness-agnostic system designed for founders and technical operators. It bridges two symmetric engines:\n1. **The Founder Operations Engine ([`/founder-mode`](../founder-mode/SKILL.md))**: High-agency leverage for sales, customer support, brand growth, product marketing, and speed-to-market.\n2. **The Engineering Engine ([`/engineer-mode`](../engineer-mode/SKILL.md))**: World-class engineering rigor with 23 playbooks, 24 design principles, multi-model panels, and zero slop.\n\n---\n\n## The Task Router\n\nWhen `fstack` is invoked, immediately classify the user's intent into one of three tracks:\n\n```mermaid\ngraph TD\n    UserRequest([User Request]) --> Router{Task Classifier}\n    \n    Router -->|\"Sales, Leads, Outbound\"| Sales[\"/lead-reply, /unslop-email, /inbox-triage\"]\n    Router -->|\"Support / Customer Bug\"| Support[\"/support-loop (Triage -> engineer-mode -> Reply)\"]\n    Router -->|\"Audience / Social / Brand\"| Social[\"/social-post, /social-reply (X vs LinkedIn)\"]\n    Router -->|\"Marketing / Launch / SEO\"| Marketing[\"/changelog-to-post, /geo-page, /customer-lens\"]\n    Router -->|\"Strategy / Sparring\"| Strategy[\"/office-hours, /ceo-review, /teardown\"]\n    Router -->|\"Code / Architecture / Bug Fix\"| Eng[\"/engineer-mode (23 playbooks + 24 principles)\"]\n    Router -->|\"End-to-End Delivery\"| FullLoop[\"Full Founder Loop: Strategy -> Build -> Announce\"]\n```\n\n### Track 1: Founder Operations (Go-To-Market, Sales, Brand, Support)\n- **Inbound Lead / Outbound Pitch** → Route to `/lead-reply` and polish with `/unslop-email`.\n- **Customer Issue / Support Ticket** → Route to `/support-loop`.\n- **Social Media Post or Growth Reply** → Route to `/social-post` or `/social-reply`.\n- **Product Release / Changelog** → Route to `/changelog-to-post`.\n- **Competitor Analysis / Pricing Research** → Route to `/teardown` and `/browse`.\n- **Strategy & Idea Stress-Test** → Route to `/office-hours` or `/ceo-review`.\n- **Weekly Review** → Route to `/retro`.\n\n### Track 2: Engineering Rigor (`engineer-mode`)\n- **Bug Fix** → `engineer-mode/playbooks/bug-fix.md` (reproduce first, root-cause, test, fix).\n- **New Feature** → `engineer-mode/playbooks/feature.md` (data shape first, architect across boundaries).\n- **Refactoring** → `engineer-mode/playbooks/refactoring.md` (behavior-preserving, model-the-domain).\n- **Performance** → `engineer-mode/playbooks/perf-issue.md` (measure baseline, trace, verify win).\n- **Review / Pre-PR** → `/interrogate`, `/deslop`, `/no-comments`, `/technical-writing`.\n\n### Track 3: The Full Founder Loop (End-to-End)\nWhen a request bridges business and code (e.g. *\"Customer X complained about CSV exports breaking on safari, let's fix it, deploy, and reply to them\"*):\n1. **Triage & Context**: Identify customer pain, relevant files, and user expectations (`/support-loop`).\n2. **Execute with Rigor**: Transition into `engineer-mode` (Bug-Fix playbook: write reproduction script/test, fix root cause, verify).\n3. **Close the Loop**: Draft the human, context-aware reply for Customer X and update the changelog (`/changelog-to-post`).\n\n---\n\n## Universal Guidelines\n\n1. **No AI Slop Anywhere**:\n   - In code: No gratuitous wrappers, no narrating comments (`// increment counter`), no dead abstractions.\n   - In prose: No *\"In today's fast-paced digital landscape\"*, no *\"delve\"*, no *\"comprehensive\"*, no corporate throat-clearing.\n2. **Model Roles**:\n   - Check `models.json` for role mappings (`FastMechanical`, `DeepReasoning`, `StrongestJudgment`, `ProseUnslop`, `DivergentPanel`).\n   - Default to your harness's strongest model for judgment, fast model for mechanical edits.\n3. **Platform Independence**:\n   - Works natively in Cursor, Claude Code, Antigravity, OpenAI Codex, OpenCode, Hermes, and OpenClaw.\n"
}

SHA-256 of public snapshot: 670f8ad802a9870cb2a87361d66cb0ad1eca86f9b8f56064523434f8d85d8712