business-doc-pipeline

To manage an end-to-end workflow for business documents like project proposals, this skill detects the current stage, recommends the next action, and routes tasks to the correct writer or reviewer skill. It orchestrates the pipeline from discovery through drafting, revision, and finalization.

The best way to handle document review handoffs is by enforcing structured, checkpointed transitions. This skill maintains an audit trail for revisions and finalization, ensuring moving from draft to review to revision avoids messy handoffs and preserves governance.

Yes, you can use this workflow orchestration for architecture designs, PRDs, implementation plans, and executive summaries. It applies stage detection and routing to coordinate the full pipeline across these common business document types.

To start converting notes into a finalized executive summary, describe your current notes or draft. The skill will identify the discovery stage, propose the next drafting action, and orchestrate the full pipeline through review and finalization.

Yes, document pipeline orchestration supports an optional sub-agent mode. This allows the skill to route specific drafting or review tasks to appropriate sub-skills while maintaining structured handoffs and audit trails.

You need a pipeline orchestrator to avoid messy handoffs and enforce checkpointed governance. Manually moving between stages risks losing context, whereas this skill automatically detects stages, recommends next actions, and maintains revision audit trails.