task-onboarding
Skill para preparar contexto de tarefas de desenvolvimento; bloqueia início se artefatos obrigatórios faltarem.
When & Why to Use This Skill
The task-onboarding skill is a specialized developer productivity tool designed to streamline the software development lifecycle by enforcing strict context preparation. It acts as a quality gate that validates the presence of essential project artifacts—such as PRDs, technical specifications, and task definitions—before allowing development work to commence. By identifying documentation gaps and generating high-density 'Quick Context' summaries, it ensures the AI agent operates with maximum accuracy and alignment with project requirements.
Use Cases
- Pre-Development Validation: Automatically verify that all mandatory documents like prd.md, techspec.md, and tasks.md are present before starting any analysis or code implementation.
- Context Optimization: Generate a concise 'Quick Context' (under 500 tokens) to provide the AI with a focused overview of goals, scope, and critical integrations, preventing token bloat.
- Project Gap Analysis: Systematically identify and report missing execution instructions, environment variables, or architectural diagrams to the user before they become blockers.
- Task Dependency Mapping: Confirm active task numbers and manage dependencies between multiple task files to maintain a consistent development state.
- Workflow Checkpointing: Establish initial context checkpoints via a context manager to track progress and ensure a recoverable state for complex engineering tasks.
| name | task-onboarding |
|---|---|
| description | Skill para preparar contexto de tarefas de desenvolvimento; bloqueia início se artefatos obrigatórios faltarem. |
Quando usar
Acionar antes de qualquer análise ou implementação para garantir contexto mínimo completo.
Objetivo
Validar presença de artefatos críticos, gerar Quick Context e registrar gaps antes de prosseguir.
Passos
- Acionar
context-managerpara gerar Quick Context (<500 tokens) cobrindo objetivo, escopo, artefatos carregados, integrações críticas, gaps. - Verificar obrigatórios:
tasks.md, todos*_*task.md,prd.md,techspec.md, instruções de execução (comandos yarn/npm, envs, deps externas). - Se faltar algo: PAUSAR, listar faltantes, solicitar ao solicitante e não avançar.
- Opcional: registrar diagramas fornecidos (arquitetura/seq/DB).
- Confirmar número da task ativa e dependências entre
n_task.md. - Registrar checkpoint inicial via context-manager.
Saídas esperadas
- Quick Context salvo pelo context-manager.
- Lista de gaps ou confirmação de completude.
- Checkpoint inicial do contexto.