skills.rest
alatyshau
alatyshauCOMMUNITY
Explore all skills by this author →
GitHub

systematic

Applies a methodical checklist-driven stance to planning, review, and verification tasks.

Updated Nov 21, 2025
Search Tags:#planning#code review#checklist#verification#systematic#thoroughness#ai stance
One-click install
npx skills add https://github.com/alatyshau/duet --skill systematic-alatyshau
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic
Source: https://github.com/alatyshau/duet/tree/main/packages/skills/stances/systematic
Command: npx skills add https://github.com/alatyshau/duet --skill systematic-alatyshau

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working on complex changes, reviews, or audits, it is easy to skip steps, jump to conclusions, or miss details that later cause costly mistakes. This Skill enforces a thorough, verification-first working style so nothing is overlooked. ## Core Features & Use Cases - Explicit Checklists: Lists everything that needs to be checked before acting and marks items off as they are completed. - Step-by-Step Verification: Verifies each step is actually complete before moving on, and reviews the whole result at the end. - Transparent Reporting: States exactly what was checked ("Verified: X, Y, Z") before drawing conclusions. - Use Case: When planning a multi-file refactor or auditing documentation, activate this stance so the AI methodically works through a checklist instead of giving a superficial "looks fine" answer. ## Quick Start Ask the AI to use the systematic stance to review your migration plan and verify every step before proceeding.

Frequently Asked Questions about systematic

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

FAQPage Schema
How do I make an AI assistant work more methodically on complex tasks?▼

Activate the systematic stance, which instructs the AI to list everything that needs checking, work through the list step by step, verify each item, and review the whole result before concluding.

What is a systematic stance for AI-assisted code review?▼

It is a behavioral instruction set that makes the AI show an explicit checklist, mark items as completed, and state what it verified before giving conclusions, instead of saying something vaguely looks fine.

When should I use the systematic stance instead of a faster approach?▼

Use it for planning complex changes, completeness-critical reviews, and documentation audits where missing something is costly. Switch to a pragmatic stance when the user explicitly wants speed or the task is trivially simple.

When should I not use a systematic review approach?▼

Avoid it for truly simple tasks like single-file obvious changes, or when the user explicitly prioritizes speed over thoroughness. In those cases the overhead of full checklists adds little value.

Does the systematic stance require any tools or dependencies?▼

No. It is a pure instruction-based Skill defined entirely in SKILL.md, with no scripts, references, assets, or external package dependencies.

Related Skills

Explore More Software Engineering Skills→
equaltoaiequaltoai
3

enumerate-changes

Converts a scoped-need into an ordered list of single-commit changes.

Official
Advanced
HohlasHohlas
3

executing-plans

Execute written implementation plans in batches with review checkpoints.

Community
Advanced
OshayrOshayr
51

wiki-read

Query the wiki to obtain cited answers with automatic research.

Community
Intermediate
timequitytimequity
6

testing-anti-patterns

Audit test suites to replace mock-focused assertions with real-behavior checks.

Official
Basic