You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior.
EnglishUse at the start of every DDT session and before any DDT pipeline action — the DDT constitution governing Iron Laws, skill priority, the 5-station spine, intent classification, and the SSoT hierarchy.
EnglishUse at the 交付 (delivery) station of DDT's 5-station spine, after 验证 station passes — produces README, deployment guide, demo script, and (via Plan 5 metrics layer) the AI efficiency ROI report. Final IL-6 evidence gate is enforced before this step.
EnglishUse whenever building or revising the system contract (architecture decisions, OpenAPI spec, data model) from an approved PRD — the 契约 station of DDT's 5-station spine. Invoke before any build-stage slice begins.
EnglishUse during a frontend slice's spec step when the convergence target is judged perceptually by a human (UI aesthetics/UX) — routes the perceptual problem to an external AI design tool (v0/figma/claude-design) and ingests the result as an SSoT-bound spec input. NOT a pipeline stage.
EnglishUse when you have a written implementation plan to execute in a separate session with review…
EnglishUse when the frontend slice does NOT route through ddt-design-source (external loop disabled) — produce production-grade frontend code directly bound to the OpenAPI contract, with full state coverage, accessibility, and resistance to "generic AI aesthetic".
EnglishUse to write a per-slice implementation spec before invoking ddt-writing-plans — the spec step of DDT's 实现 station. Required before any plan/impl can start (IL-3 will block otherwise).
EnglishUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor…
EnglishUse when completing tasks, implementing major features, or before merging to verify work meets…
EnglishUse when executing implementation plans with independent tasks in the current…
EnglishUse when encountering any bug, test failure, or unexpected behavior, before proposing…
EnglishUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before…
EnglishUse when you have a spec or requirements for a multi-step task, before touching…
English
AGENT SKILLS ATLASIncludes Ddt Brainstorming, Ddt Charter, Ddt Deliver, and other workflows.
Claude Code
Codex
Cursor
GitHub Copilot
Gemini CLISupported by the Atlas install prompt. Skill-specific requirements vary.
Pack stats
What’s included
Ddt Brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and d
Ddt Charter
Use at the start of every DDT session and before any DDT pipeline action — the DDT constitution governing Iron Laws, skill priority, the 5-station spine, intent classification, and the SSoT hierarchy.
Ddt Deliver
Use at the 交付 (delivery) station of DDT's 5-station spine, after 验证 station passes — produces README, deployment guide, demo script, and (via Plan 5 metrics layer) the AI efficiency ROI report. Final IL-6 evidence gate is enforced before this step.
Ddt Design
Use whenever building or revising the system contract (architecture decisions, OpenAPI spec, data model) from an approved PRD — the 契约 station of DDT's 5-station spine. Invoke before any build-stage slice begins.
Ddt Design Source
Use during a frontend slice's spec step when the convergence target is judged perceptually by a human (UI aesthetics/UX) — routes the perceptual problem to an external AI design tool (v0/figma/claude-design) and ingests the result as an SSoT-bound spec input. NOT a pipeline stage.
Ddt Executing Plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Ddt Frontend Craft
Use when the frontend slice does NOT route through ddt-design-source (external loop disabled) — produce production-grade frontend code directly bound to the OpenAPI contract, with full state coverage, accessibility, and resistance to "generic AI aesthetic".
Ddt Impl Spec
Use to write a per-slice implementation spec before invoking ddt-writing-plans — the spec step of DDT's 实现 station. Required before any plan/impl can start (IL-3 will block otherwise).
Ddt Receiving Review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and
Ddt Requesting Review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Ddt Subagent Driven
Use when executing implementation plans with independent tasks in the current session
Ddt Systematic Debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Ddt TDD
Use when implementing any feature or bugfix, before writing implementation code
Ddt Verification
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before makin
Ddt Writing Plans
Use when you have a spec or requirements for a multi-step task, before touching code
Quick start
- Choose your skills. Select individual skills above, or choose the entire pack.
- Copy the install prompt. Use Copy install prompt above the list.
- Send it to your agent. Paste into your coding agent’s chat. Your agent reviews the source and guides the setup.
Try it with your agent
After installation, start with a request like:
Use the Ddt Brainstorming skill to help with my task.
Ask me for the context you need before getting started.Requirements & license
- A coding agent that can access your project files and install skills.
- Your agent checks each skill’s instructions, dependencies, and permissions during setup.
- License details are not provided in these listings. Check the author’s terms before using the skills.