Create an implementation-ready HTML design document with acceptance criteria.
npx skills add https://github.com/JHostalek/dotclaude --skill plan-jhostalek
Please help me install this Agent Skill. Skill: plan Source: https://github.com/JHostalek/dotclaude/tree/main/skills/plan Command: npx skills add https://github.com/JHostalek/dotclaude --skill plan-jhostalek
This Skill turns ambiguous coding requests into a reviewed, self-contained design contract that gives both humans and fresh coding agents a clear target before implementation begins.
Use the plan skill to research the repository and create an implementation-ready HTML design document for the requested change.
High-intent search queries and answers about installing and using this skill.
To create an implementation-ready design document, research repository patterns and relevant APIs to resolve uncertainties, then define behavior, acceptance criteria, and scope in a self-contained HTML plan. This ensures both humans and coding agents have a clear target before code changes begin.
Planning code changes across multiple files requires an executor-ready contract that defines interfaces, data expectations, and intentional file modifications without prescribing statement-level implementation. This approach prevents rediscovering requirements and clarifies boundaries for fresh coding agents.
You need to generate an HTML artifact for architecture decisions when a feature involves consequential tradeoffs, unfamiliar APIs, or requires explicit human approval. The document provides visual decision aids, alternatives, and mitigations to secure approval before implementation.
Define acceptance criteria and non-goals by establishing observable acceptance boundaries and a defined scope within a design document. Citing repository precedents and relevant external evidence ensures the behavioral contracts are justified and implementation-ready.
Yes, resolving unfamiliar APIs and ambiguous behavior is supported through evidence-based planning. It researches repository patterns, relevant libraries, and prior art to create a reviewed design contract that gives coding agents a clear implementation target.
A design document for implementation planning does not prescribe statement-level implementation details. It focuses on resolving material design uncertainties and defining scope, meaning it should be paired with an executor agent to handle the actual code generation and behavioral contracts.
MINT-IALoad project documents and repository patterns to produce a phase-numbered CONTEXT.md.
aaymanasrarAnalyzes GitHub pull request CI/CD check failures and generates fix plans for user approval.
shirulotGenerate repository-grounded threat models from trust boundaries, assets, and entry points.
bahayonghangGenerate self-contained, accessible HTML artifacts for complex work outputs.
