n8n-studio:write-spec

You need to analyze the current workflow state and user requirements to generate a standardized specification document. This creates a spec.md file capturing request context, detailed change requirements, constraints, and test-verifiable completion criteria for n8n workflow planning.

A workflow specification document in TDD agent orchestration is a structured source of truth that defines request context, current state, and test-verifiable completion criteria. It ensures downstream design and TDD development cycles have reliable, reviewable constraints before implementation begins.

To structure docs for n8n workflow planning and GitHub PR readiness, create a directory structure like docs/[project_name]/yyyyMMdd-feature-summary/ and populate it with a spec.md file. This enforces consistency by capturing target workflow identifiers, constraints, and verifiable completion criteria.

You do not need an Execution ID to write a workflow spec if it is absent from the analyzed state. The specification template safely omits the Execution ID field when it is missing, while still capturing target workflow identifiers and constraints to guide safe implementation.

When generating a spec document for agent orchestration, you should include default constraints to guide safe implementation, explicit operational limitations, and test-verifiable completion criteria. These guardrails ensure the workflow automation scenarios remain reviewable and safe for downstream TDD development.

You cannot alter the section names, order, or format when creating a feature summary spec. The generation process requires using a fixed template to ensure consistency across workflow automation documents, maintaining standardized sections for current state bullets and change requirements.