ten-steps-data-quality

Plan, evaluate, and execute data quality projects with a 10-step framework.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/kotarosan-dev/02_rd --skill ten-steps-data-quality
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ten-steps-data-quality
Source: https://github.com/kotarosan-dev/02_rd/tree/main/Books/2026/02/20260208_%E3%83%87%E3%83%BC%E3%82%BF%E5%93%81%E8%B3%AA%E3%83%97%E3%83%AD%E3%82%B8%E3%82%A7%E3%82%AF%E3%83%88%20%E5%AE%9F%E8%B7%B5%E3%82%AC%E3%82%A4%E3%83%89
Command: npx skills add https://github.com/kotarosan-dev/02_rd --skill ten-steps-data-quality

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many organizations struggle to improve data quality because efforts focus on tooling or ad-hoc fixes rather than on connecting quality work to concrete business needs, sustainable processes, and clear ownership. This Skill provides a practical, repeatable framework to design, justify, execute, and sustain data quality initiatives so improvements persist beyond one-off cleanups.

Core Features & Use Cases

  • Business-driven scoping: Start from the highest-priority business need and map which data issues block that outcome.
  • End-to-end 10-step workflow: Guidance from scoping and environment analysis through evaluation, root-cause analysis, remediation, monitoring, and change management.
  • Impact justification: Techniques to collect episodes, quantify cost of low-quality data, and build ROI-based business cases for investment.
  • Use cases include launching a master-data cleanup, embedding quality checks into SDLC/migrations, setting up ongoing QA dashboards, and building a governance-backed quality program.

Quick Start

Draft a concise data quality project plan that names the primary business need, selects 2–3 evaluation axes, outlines a short baseline assessment approach, quantifies impact with at least one episode, and proposes prioritized preventive and corrective actions.

Frequently Asked Questions about ten-steps-data-quality

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

FAQPage Schema
How do I build a data quality project plan that aligns with business outcomes?▼

To build a data quality project plan aligned with business outcomes, start from your highest-priority business need, select 2–3 evaluation axes, outline a baseline assessment approach, quantify impact with episodes, and propose prioritized preventive and corrective actions.

What is the best way to quantify the business impact of low-quality data for an ROI business case?▼

The best way to quantify the business impact of low-quality data is to collect specific episodes of data failure, calculate their associated costs, and use those quantified losses to build an ROI-based business case for investing in data quality remediation.

How do I perform root-cause analysis for data quality issues during a master data cleanup?▼

To perform root-cause analysis for data quality issues during a master data cleanup, follow a structured workflow that evaluates data across multiple quality axes, traces issues back to their origins, and designs targeted remediation and prevention strategies.

Can I embed data quality checks into my SDLC and data migration processes?▼

Yes, you can embed data quality checks into SDLC and data migration processes by applying a structured 10-step framework that integrates environment analysis, evaluation, and ongoing monitoring directly into your software development and migration workflows.

When do I need to assess the POSMAD lifecycle for data governance adoption?▼

You need to assess the POSMAD lifecycle for data governance adoption when setting up ongoing QA dashboards and programs, ensuring that data quality improvements persist beyond one-off cleanups through sustainable stakeholder engagement and monitoring.

What are the limitations of ad-hoc data quality fixes compared to a structured framework?▼

Ad-hoc data quality fixes lack sustainable processes and clear ownership, meaning improvements rarely persist beyond one-off cleanups, whereas a structured framework connects quality work to concrete business needs, remediation, and ongoing monitoring.