zenflow-prompt-writer

Generate structured Zenflow commission prompts from finalized specifications.

2|Updated Apr 8, 2026

Search Tags:#automation #markdown #specification #commission #prompt #zenflow

Ready to run

npx skills add https://github.com/DojoGenesis/gateway --skill zenflow-prompt-writer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: zenflow-prompt-writer
Source: https://github.com/DojoGenesis/gateway/tree/main/plugins/specification-driven-development/skills/zenflow-prompt-writer
Command: npx skills add https://github.com/DojoGenesis/gateway --skill zenflow-prompt-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing effective Zenflow prompts is error‑prone and time‑consuming because developers must manually assemble objectives, context, requirements, file manifests, success criteria, and constraints. This Skill automates that process, turning a finalized specification into a complete, structured commission document.

Core Features & Use Cases

Structured Prompt Creation: Generates a markdown prompt with all required sections (objective, context & grounding, detailed requirements, file manifest, success criteria, constraints).
Versioned Output: Saves the prompt under a versioned directory such as prompts/v1.2.3/.
Convenient Triggering: Activate via natural language triggers like “write a Zenflow prompt” or “commission Zenflow for this spec”. Use it whenever a spec has passed the pre‑implementation checklist and you need to commission Zenflow for any implementation task.

Quick Start

Ask the Zenflow Prompt Writer to create a prompt for version v0.1.0 using the spec at docs/v0.1.0_spec.md.

Frequently Asked Questions about zenflow-prompt-writer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate a structured Zenflow commission document from a finalized specification?▼

A Zenflow commission document requires assembling objectives, context, requirements, file manifests, success criteria, and constraints. This structure ensures deterministic guidance for Zenflow implementation tasks once a specification is approved.

When do I need to create a versioned Zenflow prompt for implementation?▼

Writing Zenflow prompts manually is error-prone because developers must assemble objectives, context, requirements, file manifests, and success criteria. Automating this process turns a finalized spec into a complete, structured markdown commission document.

How do I specify file paths and versions when writing Zenflow prompts?▼

You can trigger prompt generation using natural language phrases like “write a Zenflow prompt” or “commission Zenflow for this spec” alongside specifying the target version and the finalized specification file path.

What mandatory sections are included in a generated Zenflow markdown prompt?▼

Yes, the Zenflow prompt writer works with any finalized specification format that can be referenced by a file path. It processes the spec content to output a structured markdown commission document with versioned directory paths.