Sync Specs from Session

Extract implemented session features and translate them into SPECLAN specifications.

8|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/thlandgraf/cc-marketplace --skill sync-specs-from-session
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Sync Specs from Session
Source: https://github.com/thlandgraf/cc-marketplace/tree/main/plugins/speclan/skills/sync-from-session
Command: npx skills add https://github.com/thlandgraf/cc-marketplace --skill sync-specs-from-session

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill analyzes the current session to identify implemented features and translates them into SPECLAN specifications, enabling formal documentation and traceability.

Core Features & Use Cases

  • Convert real-time session work into SPECLAN-ready feature and requirement entries.
  • Ensure specs are implementation-agnostic and focused on user-facing capabilities and business value.
  • Use cases include documenting completed features, tracking changes, and creating change requests for in-development items.

Quick Start

Summarize the current session highlights and I will generate or update SPECLAN specs accordingly.

Frequently Asked Questions about Sync Specs from Session

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

FAQPage Schema
How do I document implemented features from my session into SPECLAN specs?

To generate SPECLAN specs, summarize your session highlights and the tool extracts implemented features, translating them into formal, implementation-agnostic specifications aligned with existing SPECLAN structures.

What is the best way to create change requests for in-development features?

Creating change requests for in-development features is done by extracting active session work and translating it into SPECLAN specifications, ensuring formal traceability and alignment with existing feature documentation structures.

Can I use this to track requirements for ongoing development contexts?

Yes, you can track requirements for ongoing development contexts by analyzing the current session to identify implemented features and generating SPECLAN-ready feature and requirement entries for active work.

How do I ensure my session-generated specs are implementation-agnostic?

To ensure session-generated specs are implementation-agnostic, the tool translates implemented features into SPECLAN specifications focused on user-facing capabilities and business value rather than underlying technical implementation details.

Does this workflow require existing SPECLAN structures to function?

The workflow does not strictly require existing SPECLAN structures beforehand, as it can generate new SPECLAN entries while maintaining alignment with existing speclan structures if they are already present in your environment.

Why are my feature documentation updates missing traceability in SPECLAN?

Feature documentation updates lack traceability in SPECLAN when implemented features are not formally extracted from the session, a gap solved by translating active session work into structured specifications and change requests.