aidd-docio

Provide canonical Python entrypoints for markdown slicing, patching, and context expansion.

5|Updated Oct 9, 2025
One-click install
npx skills add https://github.com/GrinRus/ai_driven_dev --skill aidd-docio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aidd-docio
Source: https://github.com/GrinRus/ai_driven_dev/tree/main/skills/aidd-docio
Command: npx skills add https://github.com/GrinRus/ai_driven_dev --skill aidd-docio

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

DocIO provides a shared runtime with canonical entrypoints for markdown slicing, patching, and context-map operations, enabling stage skills to perform deterministic document processing without duplicating tooling.

Core Features & Use Cases

  • Canonical Python entrypoints for md_slice.py, md_patch.py, actions_validate.py, actions_apply.py, and context_expand.py used across stage skills.
  • Consistent context-map handling and docops utilities to support preflight/postflight updates and artifact generation.
  • Use Case: a stage expands a read/write map and patches Markdown sections to produce stable context packs for a ticket.

Quick Start

Invoke the canonical DocIO entrypoint modules (md_slice, md_patch, context_expand) from your stage workflow to perform deterministic markdown operations.

Frequently Asked Questions about aidd-docio

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

FAQPage Schema
How do I slice and patch Markdown sections deterministically in an automated workflow?

Markdown slicing and patching can be performed deterministically by invoking canonical Python entrypoints like md_slice and md_patch, which provide battle-tested utilities for consistent document operations without duplicating tooling.

What is a shared runtime for Markdown context expansion and validation?

A shared Markdown runtime provides canonical entrypoints like context_expand and actions_validate to execute deterministic document processing, ensuring strict input validation and consistent artifact generation across multiple stage skills.

How do I validate actions before applying patches to Markdown files?

Actions validation is handled through canonical Python entrypoints such as actions_validate and actions_apply, enabling strict input validation and deterministic document patching before finalizing Markdown artifacts.

Can I use these Markdown document operations without integrating into a broader stage workflow?

These Markdown document operations are designed to serve stage skills across a unified runtime ecosystem, providing standardized context-map handling and preflight updates rather than functioning as a standalone utility.

Does this Markdown runtime require external dependencies for context-map handling?

No external dependencies are required, as the Markdown runtime operates with zero listed dependencies, relying entirely on its internal canonical Python entrypoints for context-map handling and document operations.

When should I use a shared runtime for Markdown document processing instead of custom scripts?

A shared Markdown runtime should be used when stage skills need deterministic document operations, strict input validation, and unified API integration, preventing the tooling duplication inherent in custom scripts.