Confidence Check

Assess pre-implementation readiness with duplicate, architecture, docs, OSS, and root-cause checks.

Updated Jan 19, 2026
One-click install
npx skills add https://github.com/jgeldart/github-copilot-plugins --skill confidence-check-jgeldart
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Confidence Check
Source: https://github.com/jgeldart/github-copilot-plugins/tree/main/.github/skills/confidence-check
Command: npx skills add https://github.com/jgeldart/github-copilot-plugins --skill confidence-check-jgeldart

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-implementation confidence assessment helps teams verify readiness before starting implementation by performing checks for duplicates, architecture, official docs, OSS references, and root-cause identification.

Core Features & Use Cases

  • Performs duplicate checks to avoid reimplementation.
  • Verifies architecture compliance and alignment with existing tech stack.
  • Confirms official documentation review and validation.
  • References working OSS implementations to guide decisions.
  • Identifies root cause to ensure the solution targets the actual problem.

Quick Start

Run the Confidence Checker with a context object that includes flags for duplication, architecture, docs, OSS reference, and root-cause. Provide details like task name, test files, and markers to tailor the assessment.

Frequently Asked Questions about Confidence Check

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

FAQPage Schema
How do I verify architecture compliance and check for duplicate implementations before starting a coding task?

Pre-implementation confidence assessment verifies architecture compliance and checks for duplicate implementations by evaluating your task context against existing tech stack alignment, producing a confidence score and recommended action to guide your execution decisions.

What is a pre-implementation confidence check in software engineering?

A pre-implementation confidence check is a readiness verification process that applies checks for duplicate implementations, architecture compliance, official documentation validation, OSS references, and root-cause identification to determine if a task should proceed.

How do I run a pre-implementation readiness assessment using a context object?

Run the confidence checker by providing a context object with flags for duplication, architecture, docs, OSS reference, and root-cause, including details like task name, test files, and markers to tailor the assessment and output a confidence score.

Can I use pre-implementation confidence checks to validate official documentation and OSS references?

Yes, the pre-implementation confidence check confirms official documentation review and validates working OSS references to guide implementation decisions, outputting a confidence score and recommended action based on these verifications.

Does pre-implementation confidence assessment help identify root cause before implementation?

Pre-implementation confidence assessment identifies root cause to ensure your solution targets the actual problem, verifying readiness through root-cause identification checks before outputting a confidence score and recommended execution action.

What's the best way to avoid reimplementation and ensure tech stack alignment before coding?

Performing a pre-implementation confidence check is the best way to avoid reimplementation and ensure tech stack alignment, applying duplicate checks and architecture compliance verification to output a readiness confidence score and recommended action.