sdcorejs-auto-specs

Capture approved spec decisions as immutable snapshots in target projects.

2|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/sdcorejs/sdcorejs-agent --skill sdcorejs-auto-specs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdcorejs-auto-specs
Source: https://github.com/sdcorejs/sdcorejs-agent/tree/main/plugin/skills/sdcorejs-auto-specs
Command: npx skills add https://github.com/sdcorejs/sdcorejs-agent --skill sdcorejs-auto-specs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents future sessions from regenerating specs with inconsistent structure and wording by persisting the exact user-approved decision contract.

Core Features & Use Cases

  • Auto-trigger after spec approval: Writes a new immutable snapshot immediately after 04-review-spec receives an explicit affirmative and before 05-plan.
  • Session-start corpus loading (read-only): Loads the latest 3 approved specs as style references for 03-write-spec without writing new files.
  • Track-aware approved-spec archive: Stores snapshots per angular-portal, nestjs, or nextjs under .sdcorejs/specs/<track>/.

Quick Start

Ask the AI to run through 04-review-spec, then explicitly approve with “OK” to have the approved spec saved into your target project’s .sdcorejs/specs/<track>/ archive.

Frequently Asked Questions about sdcorejs-auto-specs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I persist approved spec decision contracts for consistent future planning?

To persist approved spec decision contracts, this Skill captures user-approved specs and saves them as immutable timestamped snapshots in your project's `.sdcorejs/specs/` directory. This ensures future sessions load consistent style references without regenerating mismatched wording.

How do I save approved specs across angular-portal, nestjs, and nextjs workflows?

You can save approved specs across angular-portal, nestjs, and nextjs workflows by explicitly approving during the `04-review-spec` phase. The Skill then writes a track-aware immutable snapshot into the respective `.sdcorejs/specs/<track>/` folder automatically.

Why do my agent pipelines generate specs with inconsistent structure between sessions?

Agent pipelines generate inconsistent specs because previous approved decision contracts are not persisted. This Skill solves the problem by loading the latest 3 read-only approved specs at session start to mirror the user’s review language and style during spec drafting.

Does this spec persistence approach overwrite existing YAML frontmatter spec files?

No, this spec persistence approach never overwrites existing YAML frontmatter spec files. It resolves the project root using `git rev-parse` and creates new timestamped files under `.sdcorejs/specs/<track>/` to maintain an immutable archive of your decision contracts.

When do I need to load approved spec snapshots for style mirroring?

You need to load approved spec snapshots for style mirroring at session start. The Skill automatically retrieves the latest 3 approved specs in read-only mode to provide style references for the `03-write-spec` drafting phase without writing any new files.

Can I use this spec archiving tool without resolving the project root with git?

No, you cannot use this spec archiving tool without git. It requires resolving the target project root with `git rev-parse --show-toplevel` to correctly glob the `.sdcorejs/specs/<track>/*.md` directory and store the approved decision contract snapshots.