Standardized daily development workflow for incremental requirements: new features, APIs, scripts, interfaces, and optimizations. Ensures code consistency, clear progress tracking, and cross-conversation context recovery. Triggers on: "new feature", "add interface", "new script", "modify UI", "optimize performance", "fix bug","규범对齐", "add endpoint", "implement", "develop", "规范". Chinese keywords: "新功能", "新接口", "新脚本", "修改界面", "性能优化", "修复", "规范", "开发", "实现".
How this skill is triggered — by the user, by Claude, or both
Slash command
/daily-development-spec:daily-development-specThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are executing the **Daily Development Specification Workflow** — a standardized pipeline for incremental requirements (new features, APIs, scripts, interfaces). Your job is to ensure every requirement follows team standards, has clear progress tracking, and supports cross-conversation context recovery.
You are executing the Daily Development Specification Workflow — a standardized pipeline for incremental requirements (new features, APIs, scripts, interfaces). Your job is to ensure every requirement follows team standards, has clear progress tracking, and supports cross-conversation context recovery.
CRITICAL: Before starting any phase, check if docs/progress/MASTER.md already exists in the project.
After loading your current state from MASTER.md, populate the platform's native task tracking tool (e.g. TodoWrite) with the active phase's pending tasks. For each task, set content to the task description, status to "in-progress" for the currently active task and "todo" for the rest, and priority mapped as P0=high, P1=medium, P2=low. This gives the user real-time visual progress in their IDE. If no native task tool is available, skip this step — MASTER.md alone is sufficient.
Goal: Understand the requirement and select the appropriate team standard template.
Actions:
Clarify the requirement:
Select the appropriate standard template:
plugins/daily-development-spec/skills/daily-development-spec/references/scenario-templates/new_interface.mdplugins/daily-development-spec/skills/daily-development-spec/references/scenario-templates/new_script.mdplugins/daily-development-spec/skills/daily-development-spec/references/scenario-templates/new_feature.mdplugins/daily-development-spec/skills/daily-development-spec/references/scenario-templates/ui_modification.mdplugins/daily-development-spec/skills/daily-development-spec/references/scenario-templates/performance_optimization.mdReview relevant standards:
Output: Clear requirement definition + selected standard template for this task.
Goal: Verify the new code will follow team standards and design the architecture for this requirement.
Actions:
Compliance & Style Check:
Architecture Design:
Create Design Document (lightweight, in docs/progress/):
Output: Design document confirming all compliance checks passed + clear architecture for implementation.
Goal: Write code following the design and ensure quality through testing.
Actions:
Implement according to design:
Write tests:
Code Review Checklist (before submitting):
Performance Check:
Output: Complete implementation + passing test suite + code review checklist all green.
Goal: Create cross-conversation progress tracking and prepare for code delivery.
Actions:
Create progress file docs/progress/MASTER.md:
Update progress checkpoint:
Create delivery summary:
Cross-conversation continuity:
Output: Complete progress file + delivery summary ready for code review.
Goal: Conduct code review and prepare code for merge.
Actions:
Self-review checklist (before submitting to team):
Team code review (if available):
Final validation:
Prepare for merge:
Archive progress:
docs/progress/completed/Output: Code approved, tests passing, all standards met, ready for merge and deployment.
Always start with Phase 0. Clarify the requirement and select the right template. Even 2-minute requirements benefit from this clarity.
Follow the compliance checklist from Phase 1. Don't skip this—it catches style issues early and saves code review time.
Tests are required, not optional. No code ships without tests. Aim for 80%+ coverage.
Document as you code. Add comments explaining why (not what). Update README/API docs before submitting.
Use MASTER.md for state. If a requirement spans multiple conversations, save progress in docs/progress/MASTER.md. Next conversation: read MASTER.md first.
Code review checklist is your friend. Complete all items in Phase 2 before submitting to team. Saves time for everyone.
Performance matters. Measure it. If slow, optimize before submitting. Benchmark results should be in the progress file.
Commit messages tell a story. Use descriptive messages that explain what changed and why. Future you will thank you.
When in doubt, ask. Better to clarify requirements in Phase 0 than rewrite code in Phase 3.
Keep it simple. Each requirement should take 1-3 conversations. If longer, break it into smaller pieces.
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub extravert/daily-development-spec --plugin daily-development-spec