Tailmatter Commands - QA and Editorial Metadata Management #43

Closed
opened 2025-09-30 19:05:38 +00:00 by tegwick · 0 comments
Owner

UseCase: The user can access and manipulate tailmatter (QA checklists, editorial metadata, agent configurations) through dedicated CLI commands, enabling comprehensive document lifecycle and quality management.

Technical Requirements:
Implement tailmatter-stats, tailmatter-get, tailmatter-set, tailmatter-check, tailmatter-agent commands following MarkdownMatters.md specification. Support YAML/JSON fenced code blocks with 'yaml tailmatter' tags.

Acceptance Criteria:

  • Commands handle reserved namespaces (qa_checklist, editorial, agent_config), provide QA workflow support, enable editorial sign-off, maintain proper formatting, include validation

Dependencies:

  • Issue #38 Phase 1 (db-data command), MarkdownMatters.md specification, YAML/JSON parsing in fenced blocks
UseCase: The user can access and manipulate tailmatter (QA checklists, editorial metadata, agent configurations) through dedicated CLI commands, enabling comprehensive document lifecycle and quality management. Technical Requirements: Implement tailmatter-stats, tailmatter-get, tailmatter-set, tailmatter-check, tailmatter-agent commands following MarkdownMatters.md specification. Support YAML/JSON fenced code blocks with 'yaml tailmatter' tags. Acceptance Criteria: - [ ] Commands handle reserved namespaces (qa_checklist, editorial, agent_config), provide QA workflow support, enable editorial sign-off, maintain proper formatting, include validation Dependencies: - Issue #38 Phase 1 (db-data command), MarkdownMatters.md specification, YAML/JSON parsing in fenced blocks
tegwick added this to the MarkdownMatters project 2025-09-30 19:06:23 +00:00
Sign in to join this conversation.