Skip to content

Breaking change/adlc prefix migration #66

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kanfil merged 2 commits into from
Mar 5, 2026
Merged

Breaking change/adlc prefix migration #66

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4c31f62
fix: update release workflow to trigger on agentic-sdlc-v* tags
kanfil Mar 4, 2026
34ef4ae
fix: update eval prompt with correct command pattern
kanfil Mar 4, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ name: Create Release
on:
push:
tags:
- 'v*'
- 'agentic-sdlc-v*'

jobs:
release:
Expand Down
4 changes: 2 additions & 2 deletions evals/prompts/ext-prompt.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ A YAML manifest with ALL of the following fields:
- extension.author: Author name
- extension.repository: GitHub repository URL
- extension.license: License type (e.g., MIT)
- requires.speckit_version: Minimum spec-kit version (e.g., ">=0.1.0")
- requires.adlc_version: Minimum spec-kit version (e.g., ">=0.1.0")
- provides.commands: List of commands with name, file, description
- provides.config: Configuration file references
- tags: 2-5 relevant tags for catalog discovery
Expand Down Expand Up @@ -46,7 +46,7 @@ A YAML configuration file with:

IMPORTANT CONSTRAINTS:
- All YAML must be valid and parseable
- Command names must follow pattern: speckit.{extension-id}.{command-name}
- Command names must follow pattern: adlc.{extension-id}.{command-name}
- Extension ID must be lowercase with hyphens only
- Include clear CUSTOMIZE comments for user modification
- Self-contained: no references to @rule, @persona, or @example
Expand Down
Loading