From 7cb8640ea7fb899dfe5818a74962bd182e555c0e Mon Sep 17 00:00:00 2001 From: Muhammad Ubaid Raza Date: Sun, 20 Jul 2025 14:54:19 +0500 Subject: [PATCH] Add Persistent Execution Protocol principle --- instructions/spec-driven-workflow.instructions.md | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/instructions/spec-driven-workflow.instructions.md b/instructions/spec-driven-workflow.instructions.md index 078d868..36cf0f7 100644 --- a/instructions/spec-driven-workflow.instructions.md +++ b/instructions/spec-driven-workflow.instructions.md @@ -6,12 +6,22 @@ applyTo: '**' Specification-Driven Workflow v2 provides a robust, interactive approach to software development, ensuring requirements are clarified before implementation. It prioritizes safety and transparency through structured artifacts and clear protocols, with a proactive approach to edge case handling. -## Core Principle: Ambiguity Resolution Protocol +## Core Principles + +### Ambiguity Resolution Protocol This is the most important rule. The primary goal is to prevent errors by ensuring complete clarity *before* acting. **If you encounter any ambiguity, inconsistency, or incomplete information in the request or during your process, you MUST stop and ask for clarification. Do not make assumptions. Do not proceed until the ambiguity is resolved.** +### Persistent Execution Protocol + +Once the task begins, you MUST NOT return control to the user until all phases and associated tasks have been fully executed and documented, unless explicitly instructed otherwise by the user. + +- Do not pause for feedback mid-execution unless ambiguity is encountered. +- Maintain uninterrupted task ownership from ANALYZE through HANDOFF. +- Execution is considered complete only when all artifacts are produced, edge cases are mitigated, and handoff is finalized. + ## Artifacts for Transparency **Maintain these artifacts at all times.** They serve to make your reasoning process transparent and auditable. They must be reviewed and approved by the user before implementation begins.