design

Generate and revise implementation plans through iterative human annotations.

Updated Jan 1, 2012

Search Tags:#workflow #design #planning #checklist #project-management #annotation

Ready to run

npx skills add https://github.com/ysk1031/dotfiles --skill design-ysk1031

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: design
Source: https://github.com/ysk1031/dotfiles/tree/main/claude/skills/design
Command: npx skills add https://github.com/ysk1031/dotfiles --skill design-ysk1031

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Design and engineering teams often struggle to produce a clear, iteration-ready implementation plan that can be refined through explicit human feedback before any coding starts.

Core Features & Use Cases

Iterative planning loop: generate a detailed implementation plan, then revise it based on inline annotations from humans, preserving unannotated sections.
Phase-driven workflow: Phase 1 context gathering, Phase 2 plan generation, Phase 3 annotation revisions, Phase 4 finalization with a checklist for implementation.
Atomic, testable steps: each implementation step is atomic, with explicit testability considerations and a final checklist to guide handover to developers.

Quick Start

Describe the task to start Phase 1 context gathering and initiate an annotation-driven plan.

Frequently Asked Questions about design

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

FAQPage Schema

How do I create an implementation plan that supports iterative feedback before coding?▼

An iterative implementation plan is generated through a context-gathering phase, followed by human annotations that revise specific plan sections while preserving unannotated parts until final approval. This loop repeats endlessly until the plan is finalized into a checklist.

What is an annotation-driven planning workflow for complex projects?▼

Annotation-driven planning is a phase-based workflow where a generated implementation plan is refined through inline human annotations, ensuring alignment and review before development begins. It outputs a finalized, checklist-style design document for handover.

Can I revise only specific sections of a project plan without losing the rest?▼

Yes, the annotation revision phase updates the project plan based on inline human feedback while explicitly preserving unannotated sections. This ensures targeted refinements do not overwrite previously approved planning steps.

Does this planning workflow output a checklist for developers?▼

Yes, the finalization phase outputs a checklist-style design document containing atomic, testable implementation steps. This checklist guides the direct handover of the annotated project plan to the development team.

What is the best way to align design and engineering teams before starting development?▼

Aligning teams requires a structured planning workflow that gathers project context, generates an implementation plan, and refines it through annotation revisions. This explicit feedback loop ensures all stakeholders review and approve atomic steps before coding starts.

When do I need an iterative implementation plan for project management?▼

You need an iterative implementation plan for complex projects requiring explicit alignment and review before coding. It is necessary when project conventions demand structured prompts, atomic testable steps, and human annotation loops to finalize the design.