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

Add content field instruction capabilities #54

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

UseCase: As a user creating schemas for document generation, I want to include instructions for what content should go into each section, so that generated drafts provide clear guidance for content authors.

Technical Requirements:
Extend schema structure to include instruction fields that specify what type of content should be placed in each section, paragraph, or content area of documents generated from the schema.

Acceptance Criteria:

  • Schema can include content instructions for each section
  • Instructions are preserved when validating documents
  • Instructions can be displayed during document generation
  • Instructions support different content types (text, lists, requirements, etc.)
  • Instructions can be optional or required
  • Generated drafts include instruction placeholders
  • CLI supports adding instructions during schema creation

Dependencies:

  • Metaschema definition (Issue #50)
  • Heading text capture (Issue #52)
  • Current schema generation system (Issue #5)
UseCase: As a user creating schemas for document generation, I want to include instructions for what content should go into each section, so that generated drafts provide clear guidance for content authors. Technical Requirements: Extend schema structure to include instruction fields that specify what type of content should be placed in each section, paragraph, or content area of documents generated from the schema. Acceptance Criteria: - [ ] Schema can include content instructions for each section - [ ] Instructions are preserved when validating documents - [ ] Instructions can be displayed during document generation - [ ] Instructions support different content types (text, lists, requirements, etc.) - [ ] Instructions can be optional or required - [ ] Generated drafts include instruction placeholders - [ ] CLI supports adding instructions during schema creation Dependencies: - Metaschema definition (Issue #50) - Heading text capture (Issue #52) - Current schema generation system (Issue #5)
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#54
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?