Generate spec files from system overview
Generates YAML specification files from system overview using schemas and templates.
/plugin marketplace add codingawayy/cc-marketplace/plugin install specs@cc-marketplaceGenerate YAML specification files using the system overview as a guide.
Prerequisite: Run /specs:generate-overview first to create .specs/overview.md.
Read ~/.claude/plugins/cache/settings.json and get the pluginPath from the cc-specs-plugin entry.
Run the stats script to determine the current state:
pwsh -File "[pluginPath]/scripts/get-changes.ps1" -For specs
The script returns a JSON object with a type field. Based on type:
first-run → Proceed to Step 2 (full generation)no-changes → Report that specs are up to date and exitincremental → Proceed to Step 2 (incremental generation)For incremental updates, the script saves the result to .specs/temp/<prev>-to-<curr>.json.
Read .specs/overview.md to understand the system architecture.
Read the plugin folder (from pluginPath), specifically these files:
README.md - Documentation, examples, and conventionsschemas/* - Schema definitions for each spec typeCheck if a plan already exists in .specs/temp/plans/:
full-<commit>.md<prev>-to-<curr>.mdIf plan exists: Read it and continue from where it left off (some items may already be checked).
If plan does not exist: Read [pluginPath]/templates/generate-specs-plan.md and follow its instructions to create a new plan.
Execute the plan following the plan-and-do skill guidelines.
Critical: Update the plan after EACH item. For each item in the plan:
[x] Generate system.yaml (exists, valid)[x] Generate system.yaml (created)[x] Generate system.yaml (updated)Update the plan file after completing each item or small batch of related items - do not wait until the end. This ensures progress is tracked even if the session is interrupted.
Run the validation script to check the generated specs against schemas:
node "[pluginPath]/validator/validate.js"
If validation errors are found, fix them before proceeding.
Update .specs/config.json with the current commit hash as specsCommit.
For first run:
git rev-parse HEADFor incremental updates:
currentCommit from the JSON file saved in Step 1Run the summarize script to get statistics:
pwsh -File "[pluginPath]/scripts/summarize.ps1"
Report the results to the user.