do-task-strict

Execute code changes with root-cause debugging, test-first development, and review gates.

Updated May 10, 2026
One-click install
npx skills add https://github.com/lehanhhaidang/ai-skills --skill do-task-strict
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: do-task-strict
Source: https://github.com/lehanhhaidang/ai-skills/tree/main/do-task-strict
Command: npx skills add https://github.com/lehanhhaidang/ai-skills --skill do-task-strict

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pypdf, pdfplumber, pdf2image, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill unit addresses the challenge of performing code changes that may carry significant risks. It provides a stringent process for reviewing and executing changes, thereby reducing the likelihood of critical mistakes, such as those impacting security or affecting financial/billing systems.

Core Features & Use Cases

  • High-Rigor Process: Offers a maximum-rigor approach for code changes, including thorough debugging, testing, and review steps.
  • Documentation Integration: Involves comprehensive module and workflow documentation to ensure changes are grounded in reality.
  • Workflow Automation: Automates the planning, execution, and reconciliation of code changes with a detailed checklist.
  • Use Case: Suitable for critical or security-sensitive code modifications, where the potential cost of failure is high.

Quick Start

Explicitly invoke do-task-strict for any high-stakes change, such as fixing a security bug or altering money/billing logic.

Frequently Asked Questions about do-task-strict

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

FAQPage Schema
How do I ensure secure coding and rigorous validation for high-stakes code changes?

To ensure secure coding for high-stakes changes, apply a maximum-rigor process using root-cause-first debugging, test-first development, and mandatory review gates. This validates modifications against security and billing logic before completion.

What is the best way to manage change management for security-sensitive software development?

Effective change management for security-sensitive software requires comprehensive documentation integration and workflow automation. This grounds code modifications in reality by automating planning, execution, and reconciliation with detailed checklists.

How does root-cause-first debugging work when executing code changes on an indexed codebase?

Root-cause-first debugging identifies underlying issues before execution on an indexed codebase. It pairs evidence-based completion with test-first development to prevent critical mistakes in high-risk environments like financial systems.

Can I use Python libraries like pypdf and pdfplumber for command execution and system configuration?

Yes, you can use Python libraries like pypdf, pdfplumber, and pdf2image for text processing and command execution during system configuration. They support rigorous documentation and validation within the software development lifecycle.

When do I need evidence-based completion with mandatory review gates for code modifications?

You need evidence-based completion with mandatory review gates when performing critical or security-sensitive code modifications. This maximum-rigor process reduces the likelihood of critical mistakes impacting security or financial systems.