speckit-incorporate

Incorporate external documents into Speckit workflows with conflict resolution.

2|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/pradeepmouli/lspeasy --skill speckit-incorporate-pradeepmouli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-incorporate
Source: https://github.com/pradeepmouli/lspeasy/tree/main/.github/skills/speckit-incorporate
Command: npx skills add https://github.com/pradeepmouli/lspeasy --skill speckit-incorporate-pradeepmouli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Incorporate external documents into an existing or new Speckit workflow and advance stages intelligently, reducing manual handoffs and preserving context.

Core Features & Use Cases

  • Detects document type (spec, plan, tasks, research, checklist) and determines how it should influence your workflow.
  • Identifies current workflow context (not in a workflow vs inside a workflow) and the active stage to decide enrichment or progression.
  • Chooses an action strategy to enrich the appropriate stage or bridge to the next stage, including auto-creation of intermediate steps when needed.
  • Interacts with the Speckit command suite (e.g., /speckit.analyze, /speckit.plan, /speckit.tasks) to load content and merge it into the correct documents with attribution.
  • Performs conflict and duplication checks, presents options to resolve conflicts, and preserves git history and provenance for incorporated material.
  • Supports common document types such as specs, plans, tasks, research, and checklists and provides clear feedback on progress.

Quick Start

Incorporate a document into your current Speckit workflow by running /speckit.incorporate <document-path>.

Frequently Asked Questions about speckit-incorporate

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

FAQPage Schema
How do I incorporate external documents into a workflow automatically?

To incorporate external documents automatically, the Speckit workflow integration detects document types like specs, plans, and checklists, then merges content into the correct workflow stages with attribution and git history preservation.

What happens when I import conflicting documents into an existing Speckit workflow?

When importing conflicting documents, the workflow integration performs duplication checks and presents conflict resolution options, ensuring content merging is handled cleanly without overwriting existing context or losing provenance.

Can I use external research documents to advance a workflow stage that is already in progress?

Yes, you can use external research to enrich an active stage. The system detects the current workflow context and applies an action strategy to enrich the appropriate stage or bridge to the next one, auto-creating intermediate steps if needed.

Does document incorporation work with version control to preserve git history?

Yes, document incorporation preserves git history and provenance. It interacts with Speckit commands to load content and merge it into documents, maintaining version control integrity throughout the workflow integration process.

What document types are supported for automated workflow integration?

Automated workflow integration supports common document types including specs, plans, tasks, research, and checklists. The system detects the document type to determine how it should influence your workflow progression.