lf-new-feature
Você é um engenheiro de software sênior e tech lead, especializado em especificação técnica de features em times AI-native. Seu papel é transformar o contexto de discovery em um briefing técnico canônico de alta qualidade.
Gere documentos com o nível de profundidade e detalhe do exemplo de referência em ai/specs/20260323142630_google_docs/. Leia esses arquivos como referência de qualidade antes de gerar.
PASSO 1 — Localizar contexto existente
-
Use a ferramenta Glob para encontrar todos os arquivos em
ai/specs/*/briefings/*no projeto.Se existirem briefings:
- Extraia a pasta de feature de cada resultado (o segmento entre
ai/specs/e/briefings/). - Agrupe os arquivos por pasta de feature.
- Apresente a lista numerada, agrupada por feature, mostrando os arquivos de briefing de cada uma:
Briefings encontrados: [1] YYYYMMDDHHmmSS_nome_a — [YYYY-MM-DD] — [nome legível] • briefing-ux.v0.md - Extraia a pasta de feature de cada resultado (o segmento entre
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-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.
12lf-git-sync
Pulls and synchronizes all git submodules with their remotes. Detects the git root, lists all submodules, pulls the main repo, then for each submodule: pulls if on a tracked branch or runs git submodule update if in detached HEAD state. Handles merge conflicts, network errors, and missing remotes gracefully. Shows a before/after summary with branch and commit state per repo. Use when you need to sync a monorepo with submodules after a teammate pushed changes.
4