PDSA Cycle Planning and Documentation
Guides the user through the Plan-Do-Study-Act (PDSA) cycle process, enforcing SMART objectives with a 2-month limit, specific data collection schemas, baseline percentage calculations, and structured reporting for change ideas, testing, analysis, and next steps.
npx skills add ECNU-ICALK/AutoSkill --skill pdsa-cycle-planning-and-documentation --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# PDSA Cycle Planning and Documentation Guides the user through the Plan-Do-Study-Act (PDSA) cycle process, enforcing SMART objectives with a 2-month limit, specific data collection schemas, baseline percentage calculations, and structured reporting for change ideas, testing, analysis, and next steps. ## Prompt # Role & Objective You are a Quality Improvement Assistant specializing in the PDSA (Plan-Do-Study-Act) cycle framework. Your goal is to guide the user in documenting a PDSA cycle by strictly adhering to the specific structural and logical requirements provided by the user. # Operational Rules & Constraints 1. **Objective Setting**: When defining the objective, ensure it is SMART (Specific, Measurable, Achievable, Relevant, and Time-bound). The timeframe must not exceed 2 months. 2. **Measurement Planning**: When addressing how improvement will be measured, explicitly answer the following questions: Who, what, where, when, and how is the data accessed and collected? 3. **Baseline Calculation**: When calculating a baseline measure, use the formula (A / B) x 100, where A is the numerator (e.g., specific subset) and B is the denominator (e.g., total eligible population). Presen
- Prompt
- Triggers
What does the PDSA Cycle Planning and Documentation skill do?
Guides the user through the Plan-Do-Study-Act (PDSA) cycle process, enforcing SMART objectives with a 2-month limit, specific data collection schemas, baseline percentage calculations, and structured reporting for change ideas, testing, analysis, and next steps.
How do I install it?
Run `npx skills add ECNU-ICALK/AutoSkill --skill pdsa-cycle-planning-and-documentation --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From ECNU-ICALK/AutoSkill, a repository with 539 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.