Add quint-code and FPF to spec-driven development list

[Copilot]

Evaluated three repositories for inclusion in the awesome-spec-driven-development list.

Decision

Added to Tools: quint-code

• Implements hypothesis-driven specification workflow (Abduction → Deduction → Induction → Audit → Decision)
• Generates Design Rationale Records (DRRs) with assurance levels (L0/L1/L2)
• Integrates with Claude Code, Cursor, Gemini CLI, Codex CLI

Added to Standards: FPF (First Principles Framework)

• Rigorous specification framework for modeling systems, methods, and knowledge
• Provides U.MethodDescription concept for creating specifications/recipes
• Includes F-G-R assurance calculus (Formality, Scope, Reliability) for auditable specifications
• Machine-readable patterns consumable by LLMs
• Enforces strict separation of design-time specifications from run-time work

Not Added:

• mdflow - Markdown-to-CLI executor for AI prompts, not spec-driven development

Changes

• Added quint-code to Tools section in alphabetical order with description emphasizing structured reasoning and automated design rationale
• Added FPF to Standards section as a specification framework providing standards for creating rigorous, auditable specifications

Original prompt

Do the following fit well with the list? Check each of them and decide whether or not to add it

https://github.com/johnlindquist/mdflow

https://github.com/m0n0x41d/quint-code

https://github.com/ailev/FPF

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[zhimin-z]

@copilot but we have standards section sa well. I mean if anything related to spec-driven development, we should enroll it in, even if to create a new module accordingly. re-check to confirm whether or not to include it based on its relatedness to SDD

[Copilot]

@copilot but we have standards section sa well. I mean if anything related to spec-driven development, we should enroll it in, even if to create a new module accordingly. re-check to confirm whether o...

You're right! After re-examining FPF, I found it has strong relevance to spec-driven development as a specification framework. It provides:

• U.MethodDescription - A core concept for creating specifications/recipes for methods and procedures
• F-G-R assurance calculus - Standards for auditable specifications with Formality, Scope, and Reliability levels
• Machine-readable specification patterns that can be consumed by LLMs
• Strict design-time vs run-time separation - Enforces spec-before-implementation

Added FPF to the Standards section in commit 9d02eee.

[zhimin-z]

@copilot so mdflow is not fit anywhere or related to SDD?

[Copilot]

@copilot so mdflow is not fit anywhere or related to SDD?

After re-examining mdflow more carefully, I see a potential weak connection to SDD:

Possible interpretation: mdflow uses markdown files as executable specifications for AI agent workflows - essentially "specification-as-code" for AI interactions. The YAML frontmatter acts as declarative configuration specs.

However: Its primary purpose is AI agent orchestration/execution, not the SDD methodology of writing specifications before implementation. It's a tool for running AI prompts, not for driving development from specifications.

Recommendation: mdflow doesn't fit well in the current list structure. If you want to include it, we could create a new "AI Agent Tools" or "Workflow Automation" section, but it wouldn't align with the core SDD focus of the other tools which emphasize spec-first development methodology.

[Copilot]

Pull request overview

This PR adds two new entries to the awesome-spec-driven-development list after evaluating three repositories. The additions include a specification framework in the Standards section and a structured reasoning tool in the Tools section, both aligned with spec-driven development principles.

• Added FPF (First Principles Framework) to the Standards section as a rigorous specification framework
• Added quint-code to the Tools section as a structured reasoning framework for hypothesis-driven specification development
• Excluded mdflow as it was determined to be a Markdown-to-CLI executor rather than a spec-driven development tool

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.