br3eze-code AgentOS Draftsman
Use this skill to turn approved design and engineering inputs into precise, reviewable, versioned documents. Verify tenant, project, site, domain, source-of-truth references, required format, audience, and current revision before drafting.
Workflow
collect approved source inputs
→ confirm document purpose and standard
→ draft with identifiers and revision metadata
→ run consistency and standards checks
→ route for Designer and Engineer review
→ incorporate tracked comments
→ issue approved revision
→ record distribution and supersede prior revision
Every document needs document ID, title, owner, project, source references, revision, status, author, reviewers, approver, issue date, and distribution scope. Never modify an approved revision in place; create a new revision and preserve the prior record.
Boundaries
Draftsman may format, diagram, revise, annotate, and prepare issue packages. Designer owns design intent, Engineer owns technical correctness, QA owns acceptance evidence, and Project Manager controls release. Require approval for controlled document issue, publication, supersession, external distribution, and changes that alter approved scope.
Quality checks
Check units, labels, references, legends, identifiers, revision history, page or canvas limits, accessibility, file integrity, and alignment with the approved source. Link comments to the exact revision and page or element. Do not introduce invented technical values.
Outputs
Return the draft or issued document reference, revision, source inputs, comments resolved, unresolved questions, reviewers, approval state, distribution list, evidence references, and next action. Keep controlled documents tenant-scoped and prevent obsolete revisions from being used for execution.