From 87af6f670d88a5eb6d7fb2cb594e591fc017341d Mon Sep 17 00:00:00 2001 From: Vianca Date: Wed, 18 Mar 2026 10:17:34 -0700 Subject: [PATCH 1/3] docs: add Extension Comparison Guide for community extensions --- extensions/EXTENSION-COMPARISON-GUIDE.md | 58 ++++++++++++++++++++++++ extensions/EXTENSION-PUBLISHING-GUIDE.md | 9 +++- extensions/README.md | 3 +- 3 files changed, 67 insertions(+), 3 deletions(-) create mode 100644 extensions/EXTENSION-COMPARISON-GUIDE.md diff --git a/extensions/EXTENSION-COMPARISON-GUIDE.md b/extensions/EXTENSION-COMPARISON-GUIDE.md new file mode 100644 index 0000000000..85723aa8a5 --- /dev/null +++ b/extensions/EXTENSION-COMPARISON-GUIDE.md @@ -0,0 +1,58 @@ +# Extension Comparison Guide + +A quick-reference for choosing between community extensions, organized by what they operate on. + +For installation instructions, see the [Extension User Guide](EXTENSION-USER-GUIDE.md). For the full list of available extensions, see the [Community Catalog](catalog.community.json). + +## For Extension Authors + +When publishing a new extension, add a row to the appropriate category table below. If your extension doesn't fit an existing category, add a new one. + +--- + +## Docs + +Extensions that read, validate, or generate spec artifacts, plans, tasks, or project memory. + +| Extension | Phase | Effect | What It Does | +|-----------|-------|--------|--------------| +| [Understanding](https://github.com/Testimonial/understanding) | Pre-implementation | Read-only | Runs 31 IEEE/ISO metrics against your specs and reports quality scores | +| [DocGuard](https://github.com/raccioly/docguard) | Pre-implementation | Read+Write | Validates, scores, and traces docs using CDD enforcement rules and hooks | +| [Cognitive Squad](https://github.com/Testimonial/cognitive-squad) | Pre-implementation | Read+Write | Runs a multi-agent analysis pipeline before code is written | +| [V-Model](https://github.com/leocamello/spec-kit-v-model) | Pre-implementation | Read+Write | Generates paired dev specs and test specs with traceability links | +| [Iterate](https://github.com/imviancagrace/spec-kit-iterate) | During implementation | Read+Write | Lets you define a spec change and apply it to docs mid-build | +| [Spec Sync](https://github.com/bgervin/spec-kit-sync) | Anytime | Read+Write | Scans for drift between specs and code, offers AI-assisted fixes | +| [Reconcile](https://github.com/stn1slv/spec-kit-reconcile) | Post-implementation | Read+Write | Rewrites specs, plan, and tasks to match what was actually built | +| [Retrospective](https://github.com/emi-dm/spec-kit-retrospective) | Post-implementation | Read+Write | Scores spec adherence, explains where drift happened, optionally patches specs | +| [Learning](https://github.com/imviancagrace/spec-kit-learn) | Post-implementation | Read+Write | Produces educational guides from your implementation for knowledge transfer | +| [Archive](https://github.com/stn1slv/spec-kit-archive) | Post-merge | Read+Write | Merges feature knowledge into project-level memory after a feature ships | + +## Code + +Extensions that review, validate, or modify source code. + +| Extension | Phase | Effect | What It Does | +|-----------|-------|--------|--------------| +| [Fleet Orchestrator](https://github.com/sharathsatish/spec-kit-fleet) | During implementation | Read+Write | Walks through the full SDD lifecycle with human approval gates at each phase | +| [Ralph Loop](https://github.com/Rubiss/spec-kit-ralph) | During implementation | Read+Write | Hands specs to an AI agent and loops until implementation is complete | +| [Cleanup](https://github.com/dsrednicki/spec-kit-cleanup) | Post-implementation | Read+Write | Auto-fixes small tech debt, creates tasks for medium issues, reports large ones | +| [Review](https://github.com/ismaelJimenez/spec-kit-review) | Post-implementation | Read-only | Runs 7 specialized review agents across code quality, tests, types, error handling | +| [Verify](https://github.com/ismaelJimenez/spec-kit-verify) | Post-implementation | Read-only | Compares code against spec artifacts and returns a pass/fail result | + +## Third-Party Integrations + +Extensions that sync with external platforms. + +| Extension | Phase | Effect | What It Does | +|-----------|-------|--------|--------------| +| [Jira](https://github.com/mbachorik/spec-kit-jira) | Cross-cutting | Read+Write | Creates Jira Epics, Stories, and Issues from your specs and task breakdowns | +| [Azure DevOps](https://github.com/pragya247/spec-kit-azure-devops) | Cross-cutting | Read+Write | Pushes specs and tasks to Azure DevOps as work items | + +## Project Visibility + +Extensions that report on project health or workflow progress. + +| Extension | Phase | Effect | What It Does | +|-----------|-------|--------|--------------| +| [Doctor](https://github.com/KhawarHabibKhan/spec-kit-doctor) | Project setup | Read-only | Checks project structure, agents, features, scripts, extensions, and git for issues | +| [Status](https://github.com/KhawarHabibKhan/spec-kit-status) | Project setup | Read-only | Shows your active feature, artifact status, task completion, and current phase | diff --git a/extensions/EXTENSION-PUBLISHING-GUIDE.md b/extensions/EXTENSION-PUBLISHING-GUIDE.md index 39b744b2e1..42504ec739 100644 --- a/extensions/EXTENSION-PUBLISHING-GUIDE.md +++ b/extensions/EXTENSION-PUBLISHING-GUIDE.md @@ -214,14 +214,18 @@ Add your extension to the Available Extensions table in `extensions/README.md`: Insert your extension in alphabetical order in the table. -### 4. Submit Pull Request +### 4. Update Comparison Guide + +Add a row for your extension in the appropriate category table in `extensions/EXTENSION-COMPARISON-GUIDE.md`. See the [Comparison Guide](EXTENSION-COMPARISON-GUIDE.md) for instructions. + +### 5. Submit Pull Request ```bash # Create a branch git checkout -b add-your-extension # Commit your changes -git add extensions/catalog.community.json extensions/README.md +git add extensions/catalog.community.json extensions/README.md extensions/EXTENSION-COMPARISON-GUIDE.md git commit -m "Add your-extension to community catalog - Extension ID: your-extension @@ -261,6 +265,7 @@ Brief description of what your extension does. - [x] No security vulnerabilities - [x] Added to extensions/catalog.community.json - [x] Added to extensions/README.md Available Extensions table +- [x] Added to extensions/EXTENSION-COMPARISON-GUIDE.md ### Testing Tested on: diff --git a/extensions/README.md b/extensions/README.md index 954115142a..25072b137d 100644 --- a/extensions/README.md +++ b/extensions/README.md @@ -68,7 +68,7 @@ specify extension add --from https://github.com/org/spec-kit-ext/archive/refs/ta ## Available Community Extensions -The following community-contributed extensions are available in [`catalog.community.json`](catalog.community.json): +The following community-contributed extensions are available in [`catalog.community.json`](catalog.community.json). See the [Extension Comparison Guide](EXTENSION-COMPARISON-GUIDE.md) for help choosing between extensions that serve similar purposes. | Extension | Purpose | URL | |-----------|---------|-----| @@ -104,6 +104,7 @@ To add your extension to the community catalog: 3. **Submit a Pull Request** that: - Adds your extension to `extensions/catalog.community.json` - Updates this README with your extension in the Available Extensions table + - Adds a row to the [Extension Comparison Guide](EXTENSION-COMPARISON-GUIDE.md) 4. **Wait for review** - maintainers will review and merge if criteria are met See the [Extension Publishing Guide](EXTENSION-PUBLISHING-GUIDE.md) for detailed step-by-step instructions. From 6090c8c26953bc8055918f8544eb947a04b09565 Mon Sep 17 00:00:00 2001 From: Vianca Date: Wed, 18 Mar 2026 11:23:30 -0700 Subject: [PATCH 2/3] docs: delete addt. doc and just add columns to readme --- extensions/EXTENSION-COMPARISON-GUIDE.md | 58 ------------------------ extensions/EXTENSION-PUBLISHING-GUIDE.md | 9 +--- extensions/README.md | 51 +++++++++++---------- 3 files changed, 29 insertions(+), 89 deletions(-) delete mode 100644 extensions/EXTENSION-COMPARISON-GUIDE.md diff --git a/extensions/EXTENSION-COMPARISON-GUIDE.md b/extensions/EXTENSION-COMPARISON-GUIDE.md deleted file mode 100644 index 85723aa8a5..0000000000 --- a/extensions/EXTENSION-COMPARISON-GUIDE.md +++ /dev/null @@ -1,58 +0,0 @@ -# Extension Comparison Guide - -A quick-reference for choosing between community extensions, organized by what they operate on. - -For installation instructions, see the [Extension User Guide](EXTENSION-USER-GUIDE.md). For the full list of available extensions, see the [Community Catalog](catalog.community.json). - -## For Extension Authors - -When publishing a new extension, add a row to the appropriate category table below. If your extension doesn't fit an existing category, add a new one. - ---- - -## Docs - -Extensions that read, validate, or generate spec artifacts, plans, tasks, or project memory. - -| Extension | Phase | Effect | What It Does | -|-----------|-------|--------|--------------| -| [Understanding](https://github.com/Testimonial/understanding) | Pre-implementation | Read-only | Runs 31 IEEE/ISO metrics against your specs and reports quality scores | -| [DocGuard](https://github.com/raccioly/docguard) | Pre-implementation | Read+Write | Validates, scores, and traces docs using CDD enforcement rules and hooks | -| [Cognitive Squad](https://github.com/Testimonial/cognitive-squad) | Pre-implementation | Read+Write | Runs a multi-agent analysis pipeline before code is written | -| [V-Model](https://github.com/leocamello/spec-kit-v-model) | Pre-implementation | Read+Write | Generates paired dev specs and test specs with traceability links | -| [Iterate](https://github.com/imviancagrace/spec-kit-iterate) | During implementation | Read+Write | Lets you define a spec change and apply it to docs mid-build | -| [Spec Sync](https://github.com/bgervin/spec-kit-sync) | Anytime | Read+Write | Scans for drift between specs and code, offers AI-assisted fixes | -| [Reconcile](https://github.com/stn1slv/spec-kit-reconcile) | Post-implementation | Read+Write | Rewrites specs, plan, and tasks to match what was actually built | -| [Retrospective](https://github.com/emi-dm/spec-kit-retrospective) | Post-implementation | Read+Write | Scores spec adherence, explains where drift happened, optionally patches specs | -| [Learning](https://github.com/imviancagrace/spec-kit-learn) | Post-implementation | Read+Write | Produces educational guides from your implementation for knowledge transfer | -| [Archive](https://github.com/stn1slv/spec-kit-archive) | Post-merge | Read+Write | Merges feature knowledge into project-level memory after a feature ships | - -## Code - -Extensions that review, validate, or modify source code. - -| Extension | Phase | Effect | What It Does | -|-----------|-------|--------|--------------| -| [Fleet Orchestrator](https://github.com/sharathsatish/spec-kit-fleet) | During implementation | Read+Write | Walks through the full SDD lifecycle with human approval gates at each phase | -| [Ralph Loop](https://github.com/Rubiss/spec-kit-ralph) | During implementation | Read+Write | Hands specs to an AI agent and loops until implementation is complete | -| [Cleanup](https://github.com/dsrednicki/spec-kit-cleanup) | Post-implementation | Read+Write | Auto-fixes small tech debt, creates tasks for medium issues, reports large ones | -| [Review](https://github.com/ismaelJimenez/spec-kit-review) | Post-implementation | Read-only | Runs 7 specialized review agents across code quality, tests, types, error handling | -| [Verify](https://github.com/ismaelJimenez/spec-kit-verify) | Post-implementation | Read-only | Compares code against spec artifacts and returns a pass/fail result | - -## Third-Party Integrations - -Extensions that sync with external platforms. - -| Extension | Phase | Effect | What It Does | -|-----------|-------|--------|--------------| -| [Jira](https://github.com/mbachorik/spec-kit-jira) | Cross-cutting | Read+Write | Creates Jira Epics, Stories, and Issues from your specs and task breakdowns | -| [Azure DevOps](https://github.com/pragya247/spec-kit-azure-devops) | Cross-cutting | Read+Write | Pushes specs and tasks to Azure DevOps as work items | - -## Project Visibility - -Extensions that report on project health or workflow progress. - -| Extension | Phase | Effect | What It Does | -|-----------|-------|--------|--------------| -| [Doctor](https://github.com/KhawarHabibKhan/spec-kit-doctor) | Project setup | Read-only | Checks project structure, agents, features, scripts, extensions, and git for issues | -| [Status](https://github.com/KhawarHabibKhan/spec-kit-status) | Project setup | Read-only | Shows your active feature, artifact status, task completion, and current phase | diff --git a/extensions/EXTENSION-PUBLISHING-GUIDE.md b/extensions/EXTENSION-PUBLISHING-GUIDE.md index 42504ec739..39b744b2e1 100644 --- a/extensions/EXTENSION-PUBLISHING-GUIDE.md +++ b/extensions/EXTENSION-PUBLISHING-GUIDE.md @@ -214,18 +214,14 @@ Add your extension to the Available Extensions table in `extensions/README.md`: Insert your extension in alphabetical order in the table. -### 4. Update Comparison Guide - -Add a row for your extension in the appropriate category table in `extensions/EXTENSION-COMPARISON-GUIDE.md`. See the [Comparison Guide](EXTENSION-COMPARISON-GUIDE.md) for instructions. - -### 5. Submit Pull Request +### 4. Submit Pull Request ```bash # Create a branch git checkout -b add-your-extension # Commit your changes -git add extensions/catalog.community.json extensions/README.md extensions/EXTENSION-COMPARISON-GUIDE.md +git add extensions/catalog.community.json extensions/README.md git commit -m "Add your-extension to community catalog - Extension ID: your-extension @@ -265,7 +261,6 @@ Brief description of what your extension does. - [x] No security vulnerabilities - [x] Added to extensions/catalog.community.json - [x] Added to extensions/README.md Available Extensions table -- [x] Added to extensions/EXTENSION-COMPARISON-GUIDE.md ### Testing Tested on: diff --git a/extensions/README.md b/extensions/README.md index 25072b137d..492450529b 100644 --- a/extensions/README.md +++ b/extensions/README.md @@ -68,29 +68,33 @@ specify extension add --from https://github.com/org/spec-kit-ext/archive/refs/ta ## Available Community Extensions -The following community-contributed extensions are available in [`catalog.community.json`](catalog.community.json). See the [Extension Comparison Guide](EXTENSION-COMPARISON-GUIDE.md) for help choosing between extensions that serve similar purposes. - -| Extension | Purpose | URL | -|-----------|---------|-----| -| Archive Extension | Archive merged features into main project memory. | [spec-kit-archive](https://github.com/stn1slv/spec-kit-archive) | -| Azure DevOps Integration | Sync user stories and tasks to Azure DevOps work items using OAuth authentication | [spec-kit-azure-devops](https://github.com/pragya247/spec-kit-azure-devops) | -| Cleanup Extension | Post-implementation quality gate that reviews changes, fixes small issues (scout rule), creates tasks for medium issues, and generates analysis for large issues | [spec-kit-cleanup](https://github.com/dsrednicki/spec-kit-cleanup) | -| Cognitive Squad | 19-function cognitive agent squad for autonomous pre-code analysis — 7 core agents, 7 specialists, 4 learning functions with feedback loop | [cognitive-squad](https://github.com/Testimonial/cognitive-squad) | -| DocGuard — CDD Enforcement | Canonical-Driven Development enforcement. Validates, scores, and traces project documentation with automated checks, AI-driven workflows, and spec-kit hooks. Zero NPM runtime dependencies. | [spec-kit-docguard](https://github.com/raccioly/docguard) | -| Fleet Orchestrator | Orchestrate a full feature lifecycle with human-in-the-loop gates across all SpecKit phases | [spec-kit-fleet](https://github.com/sharathsatish/spec-kit-fleet) | -| Iterate | Iterate on spec documents with a two-phase define-and-apply workflow — refine specs mid-implementation and go straight back to building | [spec-kit-iterate](https://github.com/imviancagrace/spec-kit-iterate) | -| Jira Integration | Create Jira Epics, Stories, and Issues from spec-kit specifications and task breakdowns with configurable hierarchy and custom field support | [spec-kit-jira](https://github.com/mbachorik/spec-kit-jira) | -| Learning Extension | Generate educational guides from implementations and enhance clarifications with mentoring context | [spec-kit-learn](https://github.com/imviancagrace/spec-kit-learn) | -| Project Health Check | Diagnose a Spec Kit project and report health issues across structure, agents, features, scripts, extensions, and git | [spec-kit-doctor](https://github.com/KhawarHabibKhan/spec-kit-doctor) | -| Project Status | Show current SDD workflow progress — active feature, artifact status, task completion, workflow phase, and extensions summary | [spec-kit-status](https://github.com/KhawarHabibKhan/spec-kit-status) | -| Ralph Loop | Autonomous implementation loop using AI agent CLI | [spec-kit-ralph](https://github.com/Rubiss/spec-kit-ralph) | -| Reconcile Extension | Reconcile implementation drift by surgically updating feature artifacts. | [spec-kit-reconcile](https://github.com/stn1slv/spec-kit-reconcile) | -| Retrospective Extension | Post-implementation retrospective with spec adherence scoring, drift analysis, and human-gated spec updates | [spec-kit-retrospective](https://github.com/emi-dm/spec-kit-retrospective) | -| Review Extension | Post-implementation comprehensive code review with specialized agents for code quality, comments, tests, error handling, type design, and simplification | [spec-kit-review](https://github.com/ismaelJimenez/spec-kit-review) | -| Spec Sync | Detect and resolve drift between specs and implementation. AI-assisted resolution with human approval | [spec-kit-sync](https://github.com/bgervin/spec-kit-sync) | -| Understanding | Automated requirements quality analysis — 31 deterministic metrics against IEEE/ISO standards with experimental energy-based ambiguity detection | [understanding](https://github.com/Testimonial/understanding) | -| V-Model Extension Pack | Enforces V-Model paired generation of development specs and test specs with full traceability | [spec-kit-v-model](https://github.com/leocamello/spec-kit-v-model) | -| Verify Extension | Post-implementation quality gate that validates implemented code against specification artifacts | [spec-kit-verify](https://github.com/ismaelJimenez/spec-kit-verify) | +The following community-contributed extensions are available in [`catalog.community.json`](catalog.community.json): + +**Categories:** `docs` — reads, validates, or generates spec artifacts · `code` — reviews, validates, or modifies source code · `process` — orchestrates workflow across phases · `integration` — syncs with external platforms · `visibility` — reports on project health or progress + +**Effect:** `Read-only` — produces reports without modifying files · `Read+Write` — modifies files, creates artifacts, or updates specs + +| Extension | Purpose | Category | Effect | URL | +|-----------|---------|----------|--------|-----| +| Archive Extension | Archive merged features into main project memory. | `docs` | Read+Write | [spec-kit-archive](https://github.com/stn1slv/spec-kit-archive) | +| Azure DevOps Integration | Sync user stories and tasks to Azure DevOps work items using OAuth authentication | `integration` | Read+Write | [spec-kit-azure-devops](https://github.com/pragya247/spec-kit-azure-devops) | +| Cleanup Extension | Post-implementation quality gate that reviews changes, fixes small issues (scout rule), creates tasks for medium issues, and generates analysis for large issues | `code` | Read+Write | [spec-kit-cleanup](https://github.com/dsrednicki/spec-kit-cleanup) | +| Cognitive Squad | 19-function cognitive agent squad for autonomous pre-code analysis — 7 core agents, 7 specialists, 4 learning functions with feedback loop | `docs` | Read+Write | [cognitive-squad](https://github.com/Testimonial/cognitive-squad) | +| DocGuard — CDD Enforcement | Canonical-Driven Development enforcement. Validates, scores, and traces project documentation with automated checks, AI-driven workflows, and spec-kit hooks. Zero NPM runtime dependencies. | `docs` | Read+Write | [spec-kit-docguard](https://github.com/raccioly/docguard) | +| Fleet Orchestrator | Orchestrate a full feature lifecycle with human-in-the-loop gates across all SpecKit phases | `process` | Read+Write | [spec-kit-fleet](https://github.com/sharathsatish/spec-kit-fleet) | +| Iterate | Iterate on spec documents with a two-phase define-and-apply workflow — refine specs mid-implementation and go straight back to building | `docs` | Read+Write | [spec-kit-iterate](https://github.com/imviancagrace/spec-kit-iterate) | +| Jira Integration | Create Jira Epics, Stories, and Issues from spec-kit specifications and task breakdowns with configurable hierarchy and custom field support | `integration` | Read+Write | [spec-kit-jira](https://github.com/mbachorik/spec-kit-jira) | +| Learning Extension | Generate educational guides from implementations and enhance clarifications with mentoring context | `docs` | Read+Write | [spec-kit-learn](https://github.com/imviancagrace/spec-kit-learn) | +| Project Health Check | Diagnose a Spec Kit project and report health issues across structure, agents, features, scripts, extensions, and git | `visibility` | Read-only | [spec-kit-doctor](https://github.com/KhawarHabibKhan/spec-kit-doctor) | +| Project Status | Show current SDD workflow progress — active feature, artifact status, task completion, workflow phase, and extensions summary | `visibility` | Read-only | [spec-kit-status](https://github.com/KhawarHabibKhan/spec-kit-status) | +| Ralph Loop | Autonomous implementation loop using AI agent CLI | `code` | Read+Write | [spec-kit-ralph](https://github.com/Rubiss/spec-kit-ralph) | +| Reconcile Extension | Reconcile implementation drift by surgically updating feature artifacts. | `docs` | Read+Write | [spec-kit-reconcile](https://github.com/stn1slv/spec-kit-reconcile) | +| Retrospective Extension | Post-implementation retrospective with spec adherence scoring, drift analysis, and human-gated spec updates | `docs` | Read+Write | [spec-kit-retrospective](https://github.com/emi-dm/spec-kit-retrospective) | +| Review Extension | Post-implementation comprehensive code review with specialized agents for code quality, comments, tests, error handling, type design, and simplification | `code` | Read-only | [spec-kit-review](https://github.com/ismaelJimenez/spec-kit-review) | +| Spec Sync | Detect and resolve drift between specs and implementation. AI-assisted resolution with human approval | `docs` | Read+Write | [spec-kit-sync](https://github.com/bgervin/spec-kit-sync) | +| Understanding | Automated requirements quality analysis — 31 deterministic metrics against IEEE/ISO standards with experimental energy-based ambiguity detection | `docs` | Read-only | [understanding](https://github.com/Testimonial/understanding) | +| V-Model Extension Pack | Enforces V-Model paired generation of development specs and test specs with full traceability | `docs` | Read+Write | [spec-kit-v-model](https://github.com/leocamello/spec-kit-v-model) | +| Verify Extension | Post-implementation quality gate that validates implemented code against specification artifacts | `code` | Read-only | [spec-kit-verify](https://github.com/ismaelJimenez/spec-kit-verify) | ## Adding Your Extension @@ -104,7 +108,6 @@ To add your extension to the community catalog: 3. **Submit a Pull Request** that: - Adds your extension to `extensions/catalog.community.json` - Updates this README with your extension in the Available Extensions table - - Adds a row to the [Extension Comparison Guide](EXTENSION-COMPARISON-GUIDE.md) 4. **Wait for review** - maintainers will review and merge if criteria are met See the [Extension Publishing Guide](EXTENSION-PUBLISHING-GUIDE.md) for detailed step-by-step instructions. From eb39c38784e791ef62663b3de5698f5f80ec155d Mon Sep 17 00:00:00 2001 From: Vianca Date: Wed, 18 Mar 2026 13:00:28 -0700 Subject: [PATCH 3/3] docs: update publishing guide with new available extensions table format --- extensions/EXTENSION-PUBLISHING-GUIDE.md | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/extensions/EXTENSION-PUBLISHING-GUIDE.md b/extensions/EXTENSION-PUBLISHING-GUIDE.md index 39b744b2e1..dafb57166f 100644 --- a/extensions/EXTENSION-PUBLISHING-GUIDE.md +++ b/extensions/EXTENSION-PUBLISHING-GUIDE.md @@ -209,9 +209,22 @@ Edit `extensions/catalog.community.json` and add your extension: Add your extension to the Available Extensions table in `extensions/README.md`: ```markdown -| Your Extension Name | Brief description of what it does | [repo-name](https://github.com/your-org/spec-kit-your-extension) | +| Your Extension Name | Brief description of what it does | `category` | Effect | [repo-name](https://github.com/your-org/spec-kit-your-extension) | ``` +**Category** — pick the one that best fits your extension: + +- `docs` — reads, validates, or generates spec artifacts +- `code` — reviews, validates, or modifies source code +- `process` — orchestrates workflow across phases +- `integration` — syncs with external platforms +- `visibility` — reports on project health or progress + +**Effect** — choose one: + +- Read-only — produces reports without modifying files +- Read+Write — modifies files, creates artifacts, or updates specs + Insert your extension in alphabetical order in the table. ### 4. Submit Pull Request