speckit-incorporate

Incorporate external documents into Speckit workflows with type detection and stage advancement.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/refactory-lang/refactory-template --skill speckit-incorporate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-incorporate
Source: https://github.com/refactory-lang/refactory-template/tree/main/.claude/skills/speckit-incorporate
Command: npx skills add https://github.com/refactory-lang/refactory-template --skill speckit-incorporate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of incorporating external documents into existing or new software development workflows, ensuring context is maintained and stages are advanced intelligently.

Core Features & Use Cases

  • Document Type Detection: Automatically identifies the nature of input documents (spec, plan, tasks, research, etc.).
  • Workflow Context Awareness: Determines the current stage within a Speckit workflow.
  • Intelligent Stage Advancement: Moves the workflow forward to the appropriate stage based on the document type and current context.
  • Conflict Resolution: Helps manage and present potential conflicts between new and existing documentation.
  • Use Case: You receive a research paper outlining a new approach to a feature. This Skill can analyze the paper, identify it as 'research', and intelligently add its key findings to the relevant stage of your current 'enhance' workflow.

Quick Start

Use the speckit incorporate skill to add the document 'new-api-spec.md' to your current workflow.

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 an existing software development workflow?

To incorporate external documents into an existing workflow, the Skill analyzes the input file, detects its document type, and intelligently advances the workflow stage while maintaining context. It manages structured content integration and checks for conflicts within your project structure.

How does automatic document type detection work for specs and research papers?

Automatic document type detection works by analyzing the content of input files to identify their nature, such as spec, plan, tasks, or research. This identification allows the system to categorize the document and determine how it fits into the current workflow context.

Can I use this to advance workflow stages based on newly added documentation?

Yes, you can use this to advance workflow stages based on new documentation. It intelligently moves the workflow forward to the appropriate stage by matching the detected document type against the current project context and structured workflow requirements.

What is the best way to detect and resolve conflicts between new and existing documentation?

The best way to detect and resolve documentation conflicts is to use the built-in conflict resolution feature during the incorporation process. It manages and presents potential conflicts between new external documents and existing workflow content before final integration.

Do I need Speckit commands to integrate external docs into a project structure?

Yes, you need Speckit's analysis and workflow management commands. This Skill requires integration with those commands to manage document analysis, detect conflicts, and perform structured content integration within the defined project structure.

Why does adding a new document type sometimes not advance the workflow stage correctly?

If adding a new document type does not advance the workflow stage correctly, it is likely due to a mismatch between the detected document type and the current workflow context. The Skill relies on accurately identifying the document nature to determine the appropriate stage advancement.