spec-add

Append timestamped structured entries to .workflow/specs files with validation.

511|63|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/catlog22/Maestro-Flow --skill spec-add
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-add
Source: https://github.com/catlog22/Maestro-Flow/tree/main/.codex/skills/spec-add
Command: npx skills add https://github.com/catlog22/Maestro-Flow --skill spec-add

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about spec-add

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I append structured spec entries to repository documentation files?

To append structured spec entries, this skill validates categories and content, then writes timestamped headers to your specs files. It appends entries to the .workflow/specs directory and updates secondary convention files automatically.

What is the best way to automate adding coding patterns and decision logs to project specs?

Automating decision logs and coding patterns involves routing structured entries to designated markdown files. This skill appends standardized timestamped headers to learnings.md and optionally updates files like coding-conventions.md and architecture-constraints.md.

Can I record bug notes and debug learnings directly from an automated workflow?

Yes, you can record bug notes and debug learnings directly from an automated workflow by passing the category and content. The skill validates allowed types like bug, debug, and test, then appends the entry to the specs directory.

What categories are supported when adding workflow documentation entries?

Supported workflow documentation categories include bug, pattern, decision, rule, debug, test, review, and validation. The skill validates the input category against this list and returns an error code if the type is invalid.

Why does adding spec entries fail with an error when the content is missing?

Adding spec entries fails because the skill validates input content and returns specific error codes like E001 for missing content, E002 for uninitialized specs, or E003 for an invalid category, ensuring only valid entries are written.