skills

General-purpose Linear planning and creation guidance for Lightfast MCP work. Use only when the user explicitly invokes $lightfast-linear and the task involves creating, updating, triaging, or planning Linear initiatives, projects, milestones, or issues through mcp__lightfast provider routines. Do not invoke implicitly and do not use for general Linear planning outside Lightfast MCP.

Use this skill when the user wants to write, draft, update, or revise a top-level foundation document for a company, product, or new primitive. This document captures thesis, mission, boundaries, actor model, surfaces, strategic bets, and open questions without collapsing ambiguity into implementation decisions. Applies when the user is still defining what the system is, what it is not, and what long-term direction it implies. Does NOT apply to concrete service specifications in `SPEC.md`, implementation plans, PRDs, or roadmap execution docs.

Use this skill when the user wants to write, draft, update, or revise a top-level SPEC.md service specification — the language-agnostic behavioral spec that sits at a project's root and describes what a long-running service or automation does (problem statement, goals/non-goals, components, domain model). Applies when the user says things like "write a spec for X", "draft a specification", "update SPEC.md to add Y", "revise the non-goals", "add a new component to the spec", or hands over notes and asks for them to be turned into a formal service spec. Also applies when the user references an existing SPEC.md and wants edits, even if they don't explicitly use the word "spec". Covers both greenfield creation and targeted updates of an existing file. Does NOT apply to per-topic specs under thoughts/shared/specs/ (those are produced by create_ralph_topics from a JTBD), nor to JTBDs, implementation plans, or PRDs.