| name | context-ingestion |
| model | sonnet |
| description | Produces a phased, file-grounded action plan from 1-2 uploaded documents (specs, meeting notes, design docs, or code files) with concrete deliverables and binary success criteria per phase. Use when: 'create a plan from this spec', 'plan the refactoring from these files', 'what are the next steps from these docs'. |
| category | specification-driven-development |
| triggers | ["create a plan from this spec","plan the refactoring from these files","what are the next steps from these docs"] |
| tier | 1 |
| agents | ["primary"] |
| tool_dependencies | ["file_system"] |
| inputs | [{"name":"documents","type":"string[]","description":"Paths to 1-2 uploaded documents (specs, meeting notes, design docs, or code files)","required":true}] |
| outputs | [{"name":"action_plan","type":"string","description":"Phased, file-grounded action plan with concrete deliverables and binary success criteria per phase"}] |
Context Ingestion Workflow
Version: 1.0
Created: 2026-02-08
Author: Manus AI
Purpose: To create plans that are deeply informed by uploaded content, ensuring that recommendations are specific, actionable, and aligned with the provided context.
I. The Philosophy: Grounding is Everything
The quality of a plan is directly proportional to how well it is grounded in the available context. This skill transforms file uploads from passive attachments into active participants in the planning process, ensuring that every recommendation is rooted in the specifics of the provided files.
II. When to Use This Skill
- When you have 1-2 files and a general planning request (e.g., "create a plan from this spec").
- When you need to refactor a codebase and have uploaded the relevant files.
- When you want to create action items from meeting notes or a design document.
- When the
planning-with-files meta-skill routes to this mode.
III. The Workflow
This is a 5-step workflow for creating grounded plans from uploaded files.
Step 1: File Ingestion and Cataloging
Goal: Read all uploaded files and create a structured catalog of their content.
- Read Files: Use the
file tool to read each uploaded file (use view for images/PDFs).
- Extract Content: For PDFs, extract text. For code, identify structure. For images, describe visual content.
- Create Catalog: Create an internal catalog document listing all files and their key content.
Step 2: Context Synthesis
Goal: Synthesize the file content into a coherent understanding of the current state.
- Identify Patterns: Look for recurring themes, architectural decisions, and coding conventions across files.
- Extract Constraints: Note any explicit or implicit constraints (e.g., "must maintain backward compatibility").
- Identify Opportunities: Note areas for improvement or refactoring.
- Note Contradictions: If files contradict each other, call this out explicitly.
Step 3: Plan Creation
Goal: Create a detailed plan grounded in the synthesized context.
