# The Ecosystem

GitHub Spec-Kit is highly extensible. The community has developed tools to customize how the SDD workflow integrates into various environments.

#### Modularity and Presets

Spec-Kit utilizes Presets to customize agent behavior. Instead of writing a constitution from scratch for a standard React app, you can import a community preset that instantly applies React best practices, hook conventions, and state management rules. Modularity ensures that if you swap your frontend framework, you simply swap the preset—the rest of your SDD pipeline remains intact.

#### Community Extensions

Extensions hook into the Spec-Kit lifecycle to automate peripheral tasks:

* Docs Tools (`spec-kit-archive`): Automatically generates user-facing documentation and API references based on the final, verified `spec.md` and codebase.
* Code Tools (`spec-kit-review`): Acts as a secondary AI agent that strictly audits the code generated by the primary agent against the Constitution, flagging architectural deviations.
* Process Orchestrators (`spec-kit-fleet`): Designed for enterprise environments, allowing multiple AI agents to tackle parallel tasks from `tasks.md` simultaneously.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://shankar-lab.gitbook.io/mylearning/github-spec-kit/the-ecosystem.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
