Loading...
Loading...
Crea documentos técnicos organizados en /docs (specs, planes, ADRs, referencias). Usa cuando el usuario diga "crear documento", "escribir spec", "documentar esto", "creame una spec", "escribime documentación", "hacer documentación", o quiera agregar documentación al proyecto.
npx skill4agent add testacode/llm-toolkit doc-writerdocs/# Buscar carpeta docs
ls -la docs/ 2>/dev/null
# Listar subcarpetas existentes
ls -d docs/*/ 2>/dev/null| Categoria | Uso |
|---|---|
| Especificaciones de features/sistemas |
| Planes de implementacion |
| ADRs, decisiones arquitectonicas |
| Documentacion tecnica de referencia |
| Features pendientes, ideas futuras |
| Documentacion de trabajo activo |
¿En qué categoría va este documento?
☐ specs/ - Especificaciones
☐ plans/ - Planes de implementación
☐ architecture/ - ADRs, decisiones
☐ reference/ - Documentación de referencia
☐ [Otra categoría]YYYY-MM-DD-HH-MM-<feature-name>.md<feature-name>2025-12-25-14-30-user-authentication.md# [Feature Name] - Specification
## Overview
Brief description of what this feature does.
## Requirements
- [ ] Requirement 1
- [ ] Requirement 2
## Technical Approach
How this will be implemented.
## Dependencies
- Dependency 1
## Open Questions
- Question 1?# [Feature Name] - Implementation Plan
## Goal
What we're trying to achieve.
## Steps
1. Step 1
2. Step 2
## Considerations
- Risk/consideration 1
## Success Criteria
- [ ] Criteria 1# ADR: [Decision Title]
## Status
Proposed | Accepted | Deprecated | Superseded
## Context
What is the issue that we're seeing that is motivating this decision?
## Decision
What is the change that we're proposing and/or doing?
## Consequences
What becomes easier or more difficult because of this change?# [Topic] Reference
## Overview
What this document covers.
## Details
Technical details and usage.
## Examples
Code or usage examples.
## Related
- Link to related docsspecs/plans/specs/2025-12-25-15-30-authentication-system.mddocs/specs/2025-12-25-15-30-authentication-system.md