bac2b27bb8
BREAKING CHANGES: - Remove -cskill suffix from all skill names (use standard kebab-case) - Simplify marketplace.json to only official fields (fixes Issue #5) - SKILL.md body must be <500 lines (progressive disclosure via references/) New features: - Cross-platform support for 8+ platforms (Claude Code, Copilot, Cursor, Windsurf, Cline, Codex CLI, Gemini CLI) - scripts/install-template.sh: Auto-detect platform installer with --dry-run - scripts/validate.py: Spec compliance checker for generated skills - scripts/security_scan.py: Security scanner for hardcoded keys and dangerous patterns - MIGRATION.md: v3.x to v4.0 migration guide - 6 new reference files for progressive disclosure from lean SKILL.md Key changes: - SKILL.md: 4,116 → 272 lines with spec-compliant YAML frontmatter - marketplace.json: Stripped to {name, plugins} only - article-to-prototype-cskill/ → article-to-prototype/ - stock-analyzer-cskill/ → stock-analyzer/ - Export system integrates validation + security scanning - README.md rewritten for all supported platforms - Phase 5 pipeline outputs SKILL.md-first, spec-compliant skills Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
29 lines
1.2 KiB
Markdown
29 lines
1.2 KiB
Markdown
# SC-053: Backwards Compatibility with v3.x Workflows
|
|
|
|
> Covers: NFR-007 — Users can git pull and use immediately; no breaking changes to user-facing invocation
|
|
> Type: Happy Path
|
|
|
|
## Given
|
|
- A user has the v3.x version of agent-skill-creator installed via `/plugin marketplace add ./`
|
|
- The user runs `git pull` to update to v4.0
|
|
|
|
## When
|
|
- The user invokes the meta-skill with: "Create a skill for data validation"
|
|
|
|
## Then
|
|
- The meta-skill works without errors
|
|
- The 5-phase pipeline executes as before
|
|
- The trigger phrases that worked in v3.x still work
|
|
- The output is now v4.0 compliant (standard naming, no -cskill suffix) but the invocation did not break
|
|
|
|
## Verification Method
|
|
|
|
**Method**: Manual test
|
|
|
|
**Steps**:
|
|
1. From an existing v3.x installation, run: `git pull`
|
|
2. Invoke the meta-skill with a standard trigger: "Create a skill for data validation"
|
|
3. Verify the pipeline completes without errors
|
|
4. Verify the generated output is v4.0 compliant
|
|
|
|
**Expected evidence**: No errors during or after `git pull`. The meta-skill activates with the same trigger phrases. The 5 phases complete. Generated skill is v4.0 compliant (no -cskill, <500 line SKILL.md, includes install.sh).
|