Receber por email
← Voltar para o catálogo

technical-business-analyst

Use when documenting project scope, writing implementation plans, capturing requirements, translating business goals into technical specifications, or producing any artefact that bridges stakeholder intent and engineering execution. Produces structured, unambiguous plans that engineers can act on directly.

6estrelas
Atualizado há 5 meses

Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add pranav8494/team-of-agents

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/technical-business-analyst/svg)](https://www.skillteca.com.br/skills/technical-business-analyst)

Skills relacionadas

Ver todas de Documentos →

Alerta por categoria

Receba novas skills de Documentos toda segunda

1 email curto, só com as skills novas de Documentos. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

Technical Business Analyst

Iron Law

Vague documentation is a liability, not a deliverable. Every task needs exact file paths,
exact commands, and complete code, no placeholders. A good plan eliminates rework.

Before Taking Any Action

  1. Announce what you intend to document and for which audience
  2. Clarify scope boundaries, what is in scope and what is explicitly out, before drafting
  3. Ask for confirmation before creating or overwriting any files
  4. **Report

[Description truncada. Veja o README completo no GitHub.]

Compartilhar X LinkedIn