Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: ACNet-AI/MetaSpec
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v0.9.1
Choose a base ref
...
head repository: ACNet-AI/MetaSpec
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v0.9.2
Choose a head ref
  • 1 commit
  • 5 files changed
  • 1 contributor

Commits on Nov 18, 2025

  1. feat(v0.9.2): Toolkit Type Detection & Simplified Generator Pattern 

    🎯 Architecture Clarity: MetaSpec Only Generates Specification Toolkits

Critical Insight:
- MetaSpec only generates Specification Toolkits (Layer 2)
- Domain Applications (Layer 3) are separate apps built by users
- Removed confusing 'Domain Application' concept from specify.md.j2

Implemented Fixes:

1. Simplified Step 4.5 - Removed Domain Application Concept
   - Deleted 190 lines of confusing Decision Tree
   - Replaced with focused 62-line guidance
   - Clarified: All toolkits are Specification Toolkits
   - Example: marketing-spec-kit generates PROJECT FILES, not posts

2. Unified Generator Template - Removed Option B
   - Removed 'Option A/B' distinction
   - Deleted entire 'For Domain Applications' section (115 lines)
   - Single unified template for all Specification Toolkits
   - Consistent Generator architecture across all toolkits

3. Added Post-Generation Verification Checklist (Step 5d)
   - 122 lines of comprehensive verification guidance
   - Red flags detection (domain content generation)
   - Decision matrix for Generator validation
   - Links to /metaspec.sdd.analyze for automated checks

4. Updated Navigation & Removed Duplicates
   - Updated Component 5 lines: 2210-2717 (508 lines)
   - Added Step 4.5 and 5d navigation entries
   - Removed duplicate 'Domain Specification Dependencies' header
   - Updated token savings: 84-98%

Implementation Results:
- specify.md.j2: 3587 → 3463 lines (-124 lines net)
  - Deleted Domain Application content: ~250 lines
  - Added verification checklist: +122 lines
  - Removed duplicates: -8 lines
  - Navigation updates: +11 lines

Architecture Impact:
✅ Eliminates MetaSpec scope confusion
✅ Single clear pattern: All toolkits manage specifications
✅ Generator always creates project files, never domain content
✅ Early mistake detection via Step 5d checklist
✅ Perfect alignment with MetaSpec's own implementation

Quality Improvements:
- Specification generation clarity: 📈 Significantly improved
- Generator purpose clarity: 📈 Significantly improved
- Early mistake detection: 📈 New capability
- Architecture consistency: 📈 Perfect

Files Changed:
- src/metaspec/templates/meta/sdd/commands/specify.md.j2 (3463 lines)
- CHANGELOG.md (added v0.9.2 entry)
- README.md (updated version and highlights)
- pyproject.toml (version 0.9.2)
- src/metaspec/__init__.py (version 0.9.2)

Migration Path:
- Existing toolkits: Review Generator definition against Step 5d checklist
- New toolkits: Follow updated guidance automatically
- Run /metaspec.sdd.analyze for validation

Related: v0.9.1 (Generator Pattern guidance), v0.9.0 (init standards)
    @NeilJo-GY
    NeilJo-GY committed Nov 18, 2025
    Configuration menu
    Copy the full SHA
    fc171fd View commit details
    Browse the repository at this point in the history
Loading