🧩 Dev Workflow Prompt Template Generator

[Alan-Jowett]

🧩 Dev Workflow Prompt Template Generator

A PromptKit feature request to generate a complete, multi‑phase development workflow prompt set that users can add to their repos to drive structured product evolution.

This issue proposes a new PromptKit component:
a Dev Workflow Prompt Template that emits a suite of prompts enabling users to evolve their product through a consistent, auditable, multi‑step process.

The generated workflow should guide a user from requirements → design/validation → code → audit, with strict alignment enforced between each phase.

---

🎯 Goal

Enable PromptKit to generate a ready‑to‑use set of prompts that users can drop into their repositories to drive structured, iterative development of their product.

The workflow should:

1. Collaborate with the user to extract and refine requirements
2. Generate a requirements‑document patch
3. Convert the requirements patch into design + validation patches
4. Generate code + test patches based on the design/validation diffs
5. Audit each step’s output against the previous step for alignment and drift

Each phase should be implemented as a PromptKit component (persona, protocol, format, invariants).

---

📦 Deliverables

1. Requirements Collaboration Prompt

Purpose: Work interactively with the user to identify, refine, and confirm requirements.

Output:

• Structured requirements patch (diff format)
• Explicit invariants and constraints

---

2. Requirements Patch → Design & Validation Patch Generator

Purpose: Translate requirements changes into design and validation changes.

Output:

• Design patch (diff)
• Validation patch (diff)
• Invariant propagation

---

3. Design/Validation → Code Patch Generator

Purpose: Produce code and test patches strictly aligned with the design and validation diffs.

Output:

• Code patch (diff)
• Test patch (diff)
• Traceability metadata linking code → design → requirements

---

4. Multi‑Stage Audit Prompt

Purpose: Audit each phase’s output against the previous phase.

Checks:

• Requirements ↔ Design alignment
• Design ↔ Validation alignment
• Validation ↔ Code alignment
• Drift detection
• Missing invariants
• Constraint violations

Output:

• Audit report
• Severity scoring
• Suggested corrections

---

🧪 Verification Criteria

• Generated prompts follow PromptKit component structure (persona, protocol, format, invariants)
• Requirements → Design → Code patches maintain strict alignment
• Audit prompt detects mismatches and drift
• All outputs use deterministic formats suitable for CI consumption
• Workflow can be run manually or integrated into external automation

---

🧭 Notes

This feature turns PromptKit into a development workflow generator, enabling users to bootstrap a complete, structured, multi‑phase evolution pipeline for their product.

It also lays the groundwork for future:

• adversarial audits
• self‑improving workflows
• semantic CI integrations