Tag: tdd
Conteúdos públicos da tag tdd no Brabrix Skill Hub.
Conteúdos públicos da tag tdd no Brabrix Skill Hub.
334 itens
Categoria: Workflows/SDD
[High-level system design approach]
Categoria: Workflows/SDD
[Describe approach: feature-first, layered, domain-driven, etc.]
Categoria: Workflows/SDD
[Brief description of what this product does and who it serves]
Categoria: Workflows/SDD
[Purpose: guide what to test, where tests live, and how to structure them]
Categoria: Workflows/SDD
[Purpose: define security posture with patterns for validation, authz, secrets, and data]
Categoria: Workflows/SDD
[Purpose: unify how errors are classified, shaped, propagated, logged, and monitored]
Categoria: Workflows/SDD
[Purpose: safe, repeatable releases with clear environment and pipeline patterns]
Categoria: Workflows/SDD
[Purpose: guide schema design, queries, migrations, and integrity]
Categoria: Workflows/SDD
[Purpose: unify auth model, token/session lifecycle, permission checks, and security]
Categoria: Workflows/SDD
[Purpose: consistent API patterns for naming, structure, auth, versioning, and errors]
Categoria: Workflows/SDD
Use whichever pattern fits the work breakdown:
Categoria: Workflows/SDD
--- Purpose: Capture discovery findings, architectural investigations, and rationale that inform the technical design.
Categoria: Workflows/SDD
{{INTRODUCTION}}
Categoria: Workflows/SDD
{{PROJECTDESCRIPTION}}
Categoria: Workflows/SDD
--- Purpose: Provide sufficient detail to ensure implementation consistency across different implementers, preventing interpretation drift.
Categoria: Workflows/SDD
Provide a consistent way to identify implementation tasks that can be safely executed in parallel while generating tasks.md.
Categoria: Workflows/SDD
Focus on capabilities and outcomes, not code structure.
Categoria: Workflows/SDD
Steering files are project memory, not exhaustive specifications.
Categoria: Workflows/SDD
Before writing requirements.md, review the draft requirements and repair local issues until the draft passes or a true scope ambiguity is discovered.
Categoria: Workflows/SDD
Analyze the gap between requirements and existing codebase to inform implementation strategy decisions.
Categoria: Workflows/SDD
EARS (Easy Approach to Requirements Syntax) is the standard format for acceptance criteria in spec-driven development.
Categoria: Workflows/SDD
After discovery and before writing the design document, apply these three lenses to the collected findings. This step requires the full picture — do not parallelize.
Categoria: Workflows/SDD
Conduct interactive quality review of technical design documents to ensure they are solid enough to proceed to implementation with acceptable risk.
Categoria: Workflows/SDD
Before writing design.md, review the draft design and repair local issues until the design passes or a true spec gap is discovered.