spec-stack

Analyzes stack change impact and creates architecture decision records for LiveSpec projects.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/julien-m/livespec --skill spec-stack-julien-m
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-stack
Source: https://github.com/julien-m/livespec/tree/main/.agent-sync/skills/spec-stack
Command: npx skills add https://github.com/julien-m/livespec --skill spec-stack-julien-m

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Changing a technology stack component (database, auth, hosting) without knowing which features break leads to unplanned migration work and lost architectural context. This Skill shows the current stack, analyzes the impact of proposed changes across all feature specs, and records decisions as ADRs. ## Core Features & Use Cases - Stack Visibility: Displays the current stack table from .specs/stacks/_default.md along with all architecture decision records. - Impact Analysis: Scans every feature's spec, plan, and implementation files to rate change impact as High, Medium, or Low, with effort estimates and migration strategy (big-bang, phased, hybrid) plus rollback requirements. - ADR Management: Creates dated ADR files, updates the decisions table in .specs/README.md, refreshes the preflight manifest, and optionally spawns migration specs per affected feature. - Use Case: Before switching from Supabase to Firebase, run the change command to see that 4 features are affected, get a 9-12 day effort estimate, and generate an ADR documenting the decision and consequences. ## Quick Start Ask the AI to run /spec-stack change followed by a description like "switch database to Firebase" to get an impact analysis and a draft ADR.

Frequently Asked Questions about spec-stack

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

FAQPage Schema
How do I analyze the impact of changing my database or stack?

Run /spec-stack change with a description like "switch database to Firebase". The command reads all feature specs, plans, and implementation files, then produces an impact table rating each feature High, Medium, or Low with effort estimates.

How do I create an architecture decision record (ADR)?

Use /spec-stack change and confirm the proposed change. The command generates an ADR file in .specs/stacks/decisions/ with context, decision, consequences, and affected features, then updates the decisions table in .specs/README.md.

Can I preview a stack change without modifying any files?

Yes, use the --dry-run or -d flag, or run /spec-stack impact with a hypothetical change description. This shows the full impact analysis without creating ADRs or updating stack files.

What happens to my feature specs after a stack change?

After creating the ADR, the command offers to spawn /spec-specify sub-agents for each High or Medium impact feature, generating migration specs with the technical changes needed. You can skip this with --no-migration-specs.

Why does /spec-stack report BLOCKED at step 0?

Step 0 requires the livespec goal render command and an available /goal slash command to lock the goal contract. If either is missing or another goal is already active, the command stops with a BLOCKED status until the prerequisite is resolved.