devflow-engine 1.0.0__py3-none-any.whl

devflow_engine/prompts/source_doc_mutation/project_doc_render/prompt.md

@@ -0,0 +1,9 @@
+# Source Doc Mutation Project Doc Render
+
+- Render exactly one rich markdown project doc for the assigned project doc area.
+- Use the supplied project-doc richness contract, agent contract, source-to-project-doc reference map, and cross-reference rules as grounding support contracts.
+- Ground the doc in the supplied canonical source docs and routed impact packet.
+- Mutate the existing project doc when one is supplied; preserve product identity, core domain, actors, and unaffected grounded behavior.
+- Do not replace the product with a different domain, company, dashboard, or use case.
+- Do not silently contradict source docs; surface assumptions explicitly where they materially shape the document.
+- Do not fake breadth unsupported by source evidence; if source grounding is thin, say so plainly inside the document.

devflow_engine/prompts/source_doc_mutation/source_doc_coherence/prompt.md

@@ -0,0 +1,5 @@
+# Source Doc Mutation Source Doc Coherence
+
+- Review the three canonical source-doc section outputs plus assumptions registry for cross-doc coherence.
+- Return a full docs map for canonical source docs and the reconciled assumptions list.
+- Preserve grounded facts; do not invent unsupported claims.

devflow_engine/prompts/source_doc_mutation/source_doc_enrichment_coherence/prompt.md

@@ -0,0 +1,6 @@
+# Source Doc Mutation Source Doc Enrichment Coherence
+
+- This pass sits after section reconciliation but before project-doc routing/sync.
+- Strengthen sparse source docs only where needed so the canonical docs are coherent, compact, and assumption-aware.
+- Prefer minimal enrichment that improves cross-doc sufficiency, especially workflows/entities/relationships/constraints/success criteria needed by downstream project-doc sync.
+- Do not bloat source docs into pseudo-project-docs; preserve concise canonical shape.

devflow_engine/prompts/source_doc_mutation/user_workflows/prompt.md

@@ -0,0 +1,6 @@
+# Source Doc Mutation User Workflows
+
+- Own only user_workflows.json.
+- Return actors, primary flows, alternates, edge cases, and workflow assumptions.
+- In sparse scenarios, preserve at least one compact trigger-to-result workflow with key steps so downstream UX/PRD sync has real flow shape to work from.
+- Keep workflows compact and assumption-aware; do not explode them into story-level decomposition.

devflow_engine/prompts/source_scope/doctrine/prompt.md

@@ -0,0 +1,10 @@
+# Source Scope Doctrine
+
+- Preserve upstream source truth; enrich it without silently rewriting affirmed intent.
+- Return JSON only. No markdown. No prose outside JSON.
+- Keep all assumptions explicit and reviewable.
+- Prefer evidence-backed scope boundaries over shallow feature lists.
+- Use deterministic hints as scaffolding, not as a limit when stronger source evidence exists.
+- Prefer stakeholder-facing product surfaces and approved business domains over technically neat migration slices when choosing top-level scope units.
+- Do not elevate a structural change into a top-level scope item when it is better expressed as a migration package or cross-cutting constraint.
+- Preserve role-based experience domains such as admin, manager, participant, engagement lifecycle, and onboarding/add-organization when sources support them.

devflow_engine/prompts/ui_grounding/doctrine/prompt.md

@@ -0,0 +1,7 @@
+# UI Grounding Doctrine
+
+- Approved idea remains the anchor; enrich it without silently rewriting approved business intent.
+- Return JSON only. No markdown. No prose outside JSON.
+- UI-bearing slices must carry real UI anchors or explicit gaps; do not allow silent UI improvisation.
+- Prefer existing UI/design evidence over speculative new UI.
+- Keep assumptions and unresolved grounding questions explicit.

devflow_engine/recovery/__init__.py

@@ -0,0 +1,3 @@
+from .dag import FailureRecoveryDagResult, run_failure_recovery_dag
+
+__all__ = ["FailureRecoveryDagResult", "run_failure_recovery_dag"]