What problem does it solve?
This skill streamlines the process of recording project learnings, patterns, decisions, rules, and bugs by appending structured, timestamped entries to the repository's specs files so knowledge is discoverable and versioned.
Core Features & Use Cases
- Input parsing & validation: Extracts category and content, validates allowed types, and reports clear error codes (E001, E002, E003).
- Automated routing: Appends entries to .workflow/specs/learnings.md and updates a secondary convention file when applicable (e.g., coding-conventions.md, architecture-constraints.md).
- Consistent formatting: Writes entries using a standardized [type] [YYYY-MM-DD] header and preserves the full content body for future review.
- Use Case: Add a new coding pattern or a postmortem bug note directly from a CLI or automated workflow to keep the team's specifications current.
Quick Start
Use the spec-add skill with a category and entry text, for example: spec-add pattern Always use named exports for utility functions.