| name | zenflow-prompt-writer |
| model | sonnet |
| description | Produces a structured Zenflow commission document (Objective, Context & Grounding with pattern files, step-by-step Requirements, File Manifest, binary Success Criteria, and explicit Constraints) from a finalized spec, saved to prompts/vX.X.X/. Use when: 'write a Zenflow prompt', 'commission Zenflow for this spec', 'turn this spec into a Zenflow prompt', 'create the implementation prompt for Zenflow'. |
| category | specification-driven-development |
| triggers | ["write a Zenflow prompt","commission Zenflow for this spec","turn this spec into a Zenflow prompt","create the implementation prompt for Zenflow"] |
| tier | 1 |
| agents | ["primary"] |
| tool_dependencies | ["file_system"] |
| inputs | [{"name":"spec_path","type":"string","description":"Path to the finalized specification to convert into a Zenflow commission document","required":true},{"name":"version","type":"string","description":"Version string for the prompt (e.g. v3.1.0)","required":false}] |
| outputs | [{"name":"zenflow_prompt","type":"ref","format":"cas-ref","description":"Structured Zenflow commission document saved to prompts/vX.X.X/ with objective, context grounding, requirements, file manifest, and success criteria"}] |
Zenflow Prompt Writer Skill
Version: 1.0
Created: 2026-02-04
Author: Manus AI
Purpose: To provide a structured methodology for writing effective prompts for Zenflow, maximizing the probability of a successful, high-quality, and autonomous implementation.
I. The Philosophy: The Art of Commissioning
A prompt to Zenflow is not a command; it is a commission. It is a formal request for a work of craftsmanship. The quality of the commission directly determines the quality of the work. A vague, incomplete, or ambiguous prompt invites confusion, rework, and failure. A clear, comprehensive, and well-grounded prompt is an act of respect for the builder's time and capability.
This skill transforms prompt writing from a hopeful guess into a deliberate and rigorous engineering discipline. By following this structure, we provide Zenflow with everything it needs to succeed, enabling it to work with precision, autonomy, and a deep understanding of the existing codebase.
II. When to Use This Skill
- Always use this skill when creating a new development task for Zenflow.
- Use it after a specification has been finalized and has passed the
pre-implementation-checklist.
- Use it to break down a large specification into smaller, manageable implementation chunks for Zenflow.
III. The Prompt Writing Workflow
Step 1: Ground the Prompt in Context
Before writing, gather all necessary context. Zenflow has full access to the repository, so leverage this. Your primary job is to be an excellent librarian, pointing Zenflow to the right information.
- Link to the Specification: The prompt must always link to the final, approved specification document.
- Identify Key Patterns: Find 2-3 existing files in the codebase that Zenflow should use as a pattern for its work.
- Gather Relevant Files: List any other files Zenflow will need to read or modify.
Step 2: Write the Prompt Using the Template
Create a new markdown file for the prompt (e.g., prompts/v0.0.26/01_implement_breadcrumb.md) and fill out the template from Section IV of this skill. Be precise and thorough.
Step 3: Review the Prompt Against the Checklist
Before sending the prompt to Zenflow, review it against the quality checklist in Section V. Ensure every item is addressed. This is the final quality gate.
Step 4: Execute the Zenflow Task
With a high-quality prompt in hand, you can now confidently commission Zenflow to perform the work.
