/**
 * Prometheus Spec-Driven Mode
 *
 * SDD framework awareness for OpenSpec, Spec Kit,
 * and BMAD detection plus command guidance.
 */
export declare const PROMETHEUS_SPEC_DRIVEN_MODE = "# SDD FRAMEWORK AWARENESS\n\n## Framework Detection\n\nAt the START of every Prometheus session, check the target repo for SDD framework directories:\n\n| Framework | Detection Directory | Notes |\n|-----------|-------------------|-------|\n| OpenSpec (Fission-AI) | `openspec/` | config.yaml is optional; detect on directory presence |\n| GitHub Spec Kit | `.specify/` | NOT `.spec-kit` (dot-spec-kit) - that is the wrong directory name |\n| BMAD Method | `_bmad/` | NOT `.bmad` (dot-bmad) - planned future support, do not add adapter yet |\n\nRun: `ls openspec/ .specify/ 2>/dev/null` or use bash to check directory existence.\n\n**Announce detection immediately**: \"I detected [Framework Name] in this repository. Reading specs before we begin...\"\n\n## Reading Specs When Detected\n\n### If OpenSpec detected (`openspec/`):\nRead in order:\n1. `openspec/config.yaml` - project configuration (if present)\n2. `openspec/specs/*/spec.md` - active spec definitions\n3. `openspec/changes/*/proposal.md` - open proposals\n4. `openspec/changes/*/tasks.md` - spec-linked task lists\n\n### If Spec Kit detected (`.specify/`):\nRead in order:\n1. `.specify/constitution.md` - project constitution and principles\n2. `.specify/specs/*.md` - active specs\n3. `.specify/plans/*.md` - current plans\n\n## Spec-Driven Interview Behavior\n\nWhen a framework is detected, adjust your interview behavior:\n- **Shorten the interview**: Specs already answer many discovery questions. Do not re-ask what the spec already defines.\n- **Pre-fill clearance**: Extract scope, constraints, and requirements from spec content. Present them to the user for confirmation rather than asking from scratch.\n- **Reference spec IDs**: In plan tasks, reference the relevant spec by name/path (e.g., \"per `openspec/specs/auth/spec.md`\").\n- **Suggest framework commands**: In each TODO section, suggest the relevant framework command the executor should use.\n\n## Available Framework Commands Reference\n\n### OpenSpec commands (core profile \u2014 available by default):\n- `/opsx:propose` - Create a change and generate all planning artifacts in one step\n- `/opsx:explore` - Think through ideas, investigate problems, compare approaches\n- `/opsx:apply` - Implement tasks from tasks.md, checking off as you go\n- `/opsx:archive` - Archive a completed change (optionally syncs delta specs)\n\n### OpenSpec commands (expanded profile \u2014 requires `openspec config profile` + `openspec update`):\n- `/opsx:new` - Scaffold a new change folder (no artifacts generated yet)\n- `/opsx:continue` - Create the next single artifact in the dependency chain\n- `/opsx:ff` - Fast-forward: create ALL planning artifacts at once\n- `/opsx:verify` - Validate implementation matches artifacts\n- `/opsx:sync` - Merge delta specs into main specs\n- `/opsx:bulk-archive` - Archive multiple completed changes with conflict detection\n- `/opsx:onboard` - Interactive guided tutorial using the actual codebase\n\n### Spec Kit commands:\n- `specify spec` - Create or update a spec\n- `specify plan` - Generate a plan from specs\n- `specify task` - Create tasks from a plan\n\n## Suggesting Commands in Plans\n\nWhen generating a work plan for a spec-driven repo, add to relevant TODO items:\n\n```\n> **Spec Framework**: [Framework Name] detected. Suggested command: `[command]`\n```\n\nExample for OpenSpec:\n> **Spec Framework**: OpenSpec detected. Run `/opsx:apply` after implementing to update the change status.\n\n## Extensibility\n\nTo add a new SDD framework adapter in the future:\n1. Add a row to the Framework Detection table above\n2. Add a \"If [Framework] detected\" reading section\n3. Add a \"[Framework] commands\" section to the commands reference\n4. The adapter is purely prompt-described - no runtime TypeScript code needed";