coulomb/markitect-main
2
0
Fork 0
Code Issues 60 Pull Requests Actions 1 Projects 12 Releases 1 Wiki Activity

Schema-based draft generation #55

New Issue
Closed
opened 2025-10-01 00:11:11 +00:00 by tegwick · 0 comments
tegwick commented 2025-10-01 00:11:11 +00:00
Owner
Copy Link

UseCase: As a user with a well-defined schema, I want to generate draft documents that follow the schema structure and include content instructions, so that I can quickly create new documents with consistent formatting and guidance.

Technical Requirements:
Create a new CLI command generate-stub (or extend existing) that takes a schema file and generates a markdown document template with proper headings, structure, and content instruction placeholders.

Acceptance Criteria:

  • New CLI command for generating drafts from schemas
  • Generated drafts include proper heading hierarchy from schema
  • Generated drafts include content instruction placeholders
  • Generated drafts reference their source schema for future validation
  • CLI supports output file specification
  • Generated drafts are valid markdown files
  • Generated drafts can be validated against their source schema

Dependencies:

  • Metaschema definition (Issue #50)
  • Content field instructions (Issue #54)
  • Heading text capture (Issue #52)
  • Current stub generation (Issue #6)
UseCase: As a user with a well-defined schema, I want to generate draft documents that follow the schema structure and include content instructions, so that I can quickly create new documents with consistent formatting and guidance. Technical Requirements: Create a new CLI command generate-stub (or extend existing) that takes a schema file and generates a markdown document template with proper headings, structure, and content instruction placeholders. Acceptance Criteria: - [ ] New CLI command for generating drafts from schemas - [ ] Generated drafts include proper heading hierarchy from schema - [ ] Generated drafts include content instruction placeholders - [ ] Generated drafts reference their source schema for future validation - [ ] CLI supports output file specification - [ ] Generated drafts are valid markdown files - [ ] Generated drafts can be validated against their source schema Dependencies: - Metaschema definition (Issue #50) - Content field instructions (Issue #54) - Heading text capture (Issue #52) - Current stub generation (Issue #6)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
priority:critical
Critical priority issue
 priority:high
High priority issue
 priority:low
Low priority issue
 priority:medium
Medium priority issue
 status:active
Issues currently being worked on
 status:blocked
Issues blocked by dependencies
 status:done
Completed issues
 status:review
Issues under review
 status:todo
Issues ready to be worked on
 type:bug
Bug report
 type:documentation
Documentation update
 type:enhancement
Enhancement to existing feature
 type:feature
New feature request
 wish
Feature wishlist item - idea to be discussed and refined
 wish/archived
Archived or rejected wishlist item
 wish/discussion
Wishlist item currently being discussed and refined
 wish/draft
Wishlist item with initial draft specification
 wish/ready
Wishlist item ready to become a regular issue
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
bubble-reader tegwick
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coulomb/markitect-main#55
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?