lf-git-branch
Você é um tech lead sênior especializado em gestão de branches em monorepos com submodules. Seu papel é criar branches de forma consistente em todos os repositórios relevantes, garantindo nomenclatura uniforme e evitando estados inconsistentes.
O argumento passado pelo usuário (se houver) é: $ARGUMENTS
Execute os passos abaixo em ordem. Sempre confirme antes de executar operações.
PASSO 0 — Verificar contexto git e listar submodules
Use a ferramenta Bash:
git rev-parse --show-toplevel 2>&1
Se não for um repositório git:
More from twinfo-io/lifters-skills
lf-specs
Generates specs.md and wps.md after the UX/UI team delivers Figma screens. Reads the latest briefing-tech.vN.md, interactively collects one Figma URL per screen identified in the briefing, fetches design context via Figma MCP, creates briefing-tech.v(N+1).md with a Section 16 (Figma design references) and inline screen links, then generates specs.md (SPEC-XX per domain with 12 sections each and Figma URLs inline) and wps.md (work packages with dependency map). Run after /lf-new-feature once the UX/UI team has shared Figma screen URLs. Accepts optional feature folder name as argument.
16lf-new-feature
Generates the technical briefing (briefing-tech.vN.md, 15 sections) from an existing discovery.md. Can be called multiple times to iterate versions (v0 → v1 → v2). If briefing-ux.vN.md exists, uses it to populate personas and UX sections without repeating questions. Use when the user asks for /lf-new-feature or needs a technical briefing for a feature. Run /lf-specs after the UX/UI team delivers Figma screens to generate specs.md and wps.md.
16lf-discovery
Interactive feature discovery for product development teams. Conducts a structured 7-phase interview — collects reference documents (URLs or pasted content), extracts context from inputs, determines greenfield vs brownfield, runs targeted gap questions, researches market benchmarks via web search, and generates a discovery.md artifact. Use when starting a new feature, planning a product initiative, or when the user runs /lf-discovery.
16lf-design-system
Connects to Figma via MCP Server, extracts typography, colors, spacing, border radius, shadows and all design token definitions, and generates specs/design-system.md — the official design system source of truth for the project. Prompts for design system name and Figma URL if not provided as arguments. Use when the user runs /lf-design-system or wants to create or update the project's design system from Figma.
15lf-briefing-ux
Generates the UX/UI briefing from an existing discovery.md — personas, screen navigation map, per-screen specs with states and ASCII wireframes, user flows, microcopy, display rules, and visual references. Designed for the UX/UI team to start prototyping without a full technical briefing. Use after /lf-discovery and before /lf-new-feature. Produces briefings/briefing-ux.v0.md (or vN if iterating).
14lf-exec
Starts the execution of a specific work package (WP-XX) from a generated wps.md. Interactively lists available spec folders under specs/ and pending work packages (excluding completed ones), guides the developer through project update and branch creation (features/initials/semantic_name or current branch), then fires the execution prompt for the selected WP. No arguments required.
12