skills.rest
aRustyDev
aRustyDevCOMMUNITY
Explore all skills by this author →
Website𝕏@aRustyDevGitHub

Confidence Check

Assess pre-implementation readiness with five checks and a numeric confidence score.

1|Updated Aug 31, 2024
Search Tags:#architecture#documentation#root cause#validation#efficiency#confidence#pre-implementation
One-click install
npx skills add https://github.com/aRustyDev/dotfiles --skill confidence-check-arustydev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Confidence Check
Source: https://github.com/aRustyDev/dotfiles/tree/main/.claude/skills/confidence-check
Command: npx skills add https://github.com/aRustyDev/dotfiles --skill confidence-check-arustydev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents wasted effort and token costs by performing a pre-implementation confidence assessment, ensuring you're on the right track before starting any task.

Core Features & Use Cases

  • Duplicate Detection: Checks for existing implementations to avoid redundant work.
  • Architecture & Documentation Verification: Ensures compliance and adherence to official guidelines.
  • Root Cause Identification: Helps pinpoint the actual problem, not just symptoms.
  • Use Case: Before writing any code for a new feature, run a confidence check to confirm no similar functionality exists, the approach aligns with architecture, and all necessary documentation has been reviewed.

Quick Start

Perform a confidence check for the task "Implement user authentication with OAuth2".

Frequently Asked Questions about Confidence Check

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

FAQPage Schema
How do I verify my implementation approach is correct before writing code?▼

Run a pre-implementation confidence assessment to check for duplicate implementations, validate architecture compliance, review official documentation, and identify root causes. This prevents wasted effort and confirms readiness with a numeric confidence score and verification narrative.

What should I check before starting a new feature to avoid rework?▼

Conduct a confidence check across five validation areas: duplicate detection, architecture alignment, documentation review, working reference implementations, and root cause identification. Enforce a ≥90% confidence threshold before proceeding to implementation.

Can I use a confidence check to detect if similar functionality already exists?▼

Yes. The confidence check includes duplicate detection to identify existing implementations and prevent redundant work, helping you avoid duplicating effort across development, testing, and deployment scenarios.

Why should I perform a validation step before implementing a feature?▼

Pre-implementation validation prevents token waste and rework by confirming your approach aligns with architecture, complies with documentation, and addresses root causes rather than symptoms, saving time and resources.

What does the confidence score output tell me about task readiness?▼

The confidence score and verification narrative provide a go/no-go decision framework by quantifying readiness across architecture, documentation, and root cause analysis, guiding whether to proceed or reassess.

Related Skills

Explore More Software Engineering Skills→
excattexcatt
14

confidence-check

Assess pre-implementation confidence for coding tasks against documentation and architecture.

Community
Intermediate
myrtlepnmyrtlepn
24

review

Review code implementations against acceptance criteria and create tasks for gaps.

Community
Advanced
DergaczDergacz

10x-impl-review

Automates reviewing implementations against predefined plans and coding standards.

Community
Advanced
ysyecustysyecust
40

verification-loop

Automate end-to-end project verification across builds, type checks, linting, tests, and security scans.

Community
Intermediate