π« Toolkit to help you get started with SDD or any other process!
docs: fix heading capitalization for consistency
Jarren San Jose7ca792509bd5
diff --git a/README.md b/README.mdindex d270f63db..b6d7848e6 100644--- a/README.md+++ b/README.md@@ -20,16 +20,16 @@## Table of Contents- [π€ What is Spec-Driven Development?](#-what-is-spec-driven-development)-- [β‘ Get started](#-get-started)+- [β‘ Get Started](#-get-started)- [π½οΈ Video Overview](#οΈ-video-overview)- [π€ Supported AI Agents](#-supported-ai-agents)- [π§ Specify CLI Reference](#-specify-cli-reference)-- [π Core philosophy](#-core-philosophy)-- [π Development phases](#-development-phases)-- [π― Experimental goals](#-experimental-goals)+- [π Core Philosophy](#-core-philosophy)+- [π Development Phases](#-development-phases)+- [π― Experimental Goals](#-experimental-goals)- [π§ Prerequisites](#-prerequisites)-- [π Learn more](#-learn-more)-- [π Detailed process](#-detailed-process)+- [π Learn More](#-learn-more)+- [π Detailed Process](#-detailed-process)- [π Troubleshooting](#-troubleshooting)- [π₯ Maintainers](#-maintainers)- [π¬ Support](#-support)@@ -40,7 +40,7 @@Spec-Driven Development **flips the script** on traditional software development. For decades, code has been king β specifications were just scaffolding we built and discarded once the "real work" of coding began. Spec-Driven Development changes this: **specifications become executable**, directly generating working implementations rather than just guiding them.-## β‘ Get started+## β‘ Get Started### 1. Install Specify@@ -247,7 +247,7 @@ Additional commands for enhanced quality and validation:|------------------|------------------------------------------------------------------------------------------------|| `SPECIFY_FEATURE` | Override feature detection for non-Git repositories. Set to the feature directory name (e.g., `001-photo-albums`) to work on a specific feature when not using Git branches.<br/>**Must be set in the context of the agent you're working with prior to using `/speckit.plan` or follow-up commands. |-## π Core philosophy+## π Core PhilosophySpec-Driven Development is a structured process that emphasizes:@@ -256,7 +256,7 @@ Spec-Driven Development is a structured process that emphasizes:- **Multi-step refinement** rather than one-shot code generation from prompts- **Heavy reliance** on advanced AI model capabilities for specification interpretation-## π Development phases+## π Development Phases| Phase | Focus | Key Activities ||-------|-------|----------------|@@ -264,7 +264,7 @@ Spec-Driven Development is a structured process that emphasizes:| **Creative Exploration** | Parallel implementations | <ul><li>Explore diverse solutions</li><li>Support multiple technology stacks & architectures</li><li>Experiment with UX patterns</li></ul> || **Iterative Enhancement** ("Brownfield") | Brownfield modernization | <ul><li>Add features iteratively</li><li>Modernize legacy systems</li><li>Adapt processes</li></ul> |-## π― Experimental goals+## π― Experimental GoalsOur research and experimentation focus on:@@ -300,14 +300,14 @@ Our research and experimentation focus on:If you encounter issues with an agent, please open an issue so we can refine the integration.-## π Learn more+## π Learn More- **[Complete Spec-Driven Development Methodology](./spec-driven.md)** - Deep dive into the full process- **[Detailed Walkthrough](#-detailed-process)** - Step-by-step implementation guide----## π Detailed process+## π Detailed Process<details><summary>Click to expand the detailed step-by-step walkthrough</summary>