Instruction file imported from speclabs/devspec (.cursor/rules/devspec-workflow.mdc). Copyright stays with the author.

Devspec Workflow Rules

When the user invokes or references a /devspec.* workflow, treat it as command intent from devspec/adapters/command-registry.md.

Follow these rules:

• Read devspec/adapters/command-registry.md before acting on a devspec command.
• Preserve the original intent of the canonical Copilot prompt and agent files named in the registry.
• Use Git-tracked devspec/ artifacts for recovery before relying on chat history, Cursor memory, or user rules.
• Preserve required inputs, output artifacts, status values, gates, handoff order, and recovery behavior.
• Preserve structured question behavior from .github/prompts/PATTERNS.md#interactive-question-pattern; if clickable options are unavailable, render the same option labels as text and preserve the recommended option.
• Use devspec/glossary.md for status values.
• Use devspec/foundation/codebase-structure.md for repository access requirements.
• Use devspec/adapters/validation-flows.md for enterprise acceptance checks.
• For /devspec.diagram, keep SVG as the default output and treat any non-duplicated format= combination of svg, html, and mermaid as canonical command input. Example: format=svg, format=html, format=mermaid, format=svg+html, format=svg+mermaid, format=svg+html+mermaid, format=html+mermaid.
• Record unsupported platform behavior as a limitation instead of changing workflow semantics.

Do not recommend unregistered commands such as /devspec.plan, /devspec.architecture, /devspec.provider-integrations, /devspec.queue, or /devspec.decisions.