Menu
Use when documenting ASCP SDK feature work, package-shape decisions, workflow rules, or validation behavior before commit.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when planning or beginning the Dart SDK after the TypeScript SDK establishes the first downstream reference package.
Use when starting or continuing ASCP SDK repository work that needs intake, feature scoping, planning, checkpointing, and drift control across sessions.
Use when creating or revising the TypeScript SDK package scaffold, typed model surface, export strategy, or schema-to-type generation approach.
Use when building or revising the TypeScript SDK transport adapters, subscription flow, method wrappers, or protocol error normalization.
Use when building or revising the TypeScript SDK validation layer, event parsing, replay helpers, or schema-backed safety checks.
Use when starting or continuing ASCP repository work that needs spec intake, task planning, feature scoping, documentation checkpoints, and drift control across sessions.
| name | ascp-sdk-documentation-discipline |
| description | Use when documenting ASCP SDK feature work, package-shape decisions, workflow rules, or validation behavior before commit. |
Use this skill whenever work in the ASCP SDK repository needs documentation before commit. The goal is to make every completed SDK task understandable without forcing readers to reconstruct intent from code alone.
README.md for repository purpose, status, and onboarding contextAGENTS.md for agent workflow rules and contribution disciplineplans.md for the active scoped taskdocs/status.md for checkpointsdocs/ for architecture, validation, and workflow notesThe work is documented well enough when someone new to the task can understand what changed, why it changed, what it depends on upstream, and how to continue without private chat context.