Skip to content

Commit 5254efe

Browse files
committed
docs: update publishing guide with Category and Effect columns
The README table now has Category and Effect columns (added in #1897), but the publishing guide template still showed the old 3-column format. Update to match so extension authors know to include both fields. Made-with: Cursor
1 parent f85944a commit 5254efe

File tree

1 file changed

+14
-1
lines changed

1 file changed

+14
-1
lines changed

extensions/EXTENSION-PUBLISHING-GUIDE.md

Lines changed: 14 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -209,9 +209,22 @@ Edit `extensions/catalog.community.json` and add your extension:
209209
Add your extension to the Available Extensions table in `extensions/README.md`:
210210

211211
```markdown
212-
| Your Extension Name | Brief description of what it does | [repo-name](https://github.com/your-org/spec-kit-your-extension) |
212+
| Your Extension Name | Brief description of what it does | `category` | Effect | [repo-name](https://github.com/your-org/spec-kit-your-extension) |
213213
```
214214

215+
**Category** — pick the one that best fits your extension:
216+
217+
- `docs` — reads, validates, or generates spec artifacts
218+
- `code` — reviews, validates, or modifies source code
219+
- `process` — orchestrates workflow across phases
220+
- `integration` — syncs with external platforms
221+
- `visibility` — reports on project health or progress
222+
223+
**Effect** — choose one:
224+
225+
- `Read-only` — produces reports without modifying files
226+
- `Read+Write` — modifies files, creates artifacts, or updates specs
227+
215228
Insert your extension in alphabetical order in the table.
216229

217230
### 4. Submit Pull Request

0 commit comments

Comments
 (0)