Structured Document Companion

The problem

Writing technical specs, RFCs, or PRDs often leads to documents filled with tribal knowledge that outsiders can't follow. Solo drafting frequently results in scope creep, missed edge cases, and hours spent re-formatting rather than refining content.

What it does

• Executes a disciplined three-stage co-authoring process: context transfer, structured drafting, and reader validation.
• Facilitates a "context dump" to capture messy technical background, constraints, and stakeholder goals before writing begins.
• Builds documents iteratively, section-by-section, using targeted brainstorming and curation instead of dumping large blocks of text.
• Performs "fresh-reader" simulation to identify hidden assumptions and jargon that would confuse people outside the project team.
• Generates document scaffolds with placeholders to maintain structural integrity throughout the drafting process.

Why this beats prompting it yourself

Standard LLM prompts often generate generic, high-level fluff that lacks technical depth or specific organizational context. This skill forces a rigorous information-gathering phase and uses a section-factory approach to ensure every part of the document is vetted for accuracy and clarity. It actively prevents "passive scribe" behavior by challenging your assumptions and testing the final output against a simulated uninformed reader.

Use cases

• Drafting technical RFCs that need to survive a grueling architecture review board.
• Creating product requirement documents (PRDs) that bridge the gap between business goals and engineering constraints.
• Writing design docs for complex systems where dependencies and trade-offs must be explicit.
• Authoring internal decision records to document why a specific technical path was chosen over alternatives.

Known limitations

Requires an interactive session for context gathering. Works best when the agent has file-system access or artifact support to manage the evolving draft.