decision-capture

To automate decision logging, you provide a coordinator name and a prepared decision Markdown file path. The skill validates the YAML frontmatter, retries once on failure, and updates a decisions database for team traceability.

Validating decision frontmatter involves checking the Markdown file against a YAML schema. This skill automates the validation, retries once on frontmatter failure, and surfaces persistent issues to prevent invalid database entries.

You can use Markdown files to document team decisions for audits by recording context, rationale, and options. This skill validates the YAML frontmatter and updates a decisions database, maintaining an auditable trace for process improvements.

Recording project management decisions after a meeting requires logging context and options into a Markdown file. You provide the file path and coordinator name, and this skill validates the content and updates the decisions database.

When decision file validation fails, the workflow automatically retries the validation once. If frontmatter issues persist, the system surfaces the errors to the user to prevent invalid data from entering the decisions database.

Yes, you need a prepared Markdown file path to start logging a team decision. The skill extracts the context and rationale from this file, validates the YAML frontmatter, and updates the decisions database for traceability.