Skip to content
cccskills
FreePublished on GitHub

validate-implementation-plan

Validate whether an implementation plan can achieve its stated outcome before execution. Use to check requirement coverage, task contracts, dependencies, data/artifact flow, testability, ownership, impact coverage, and executable ordering without checking whether implementation already exists.

The English summary is being prepared. Showing the original description.

See how to install

Files included (2)

  • SKILL.md2.1 KB
  • SKILL-GOALS.md342 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Validate an Implementation Plan

Validate plans goal-backward. Plan completeness is not goal achievement.

  1. Establish the intended outcome, requirements, constraints, and authoritative impact set.
  2. Map each requirement to task outcomes and acceptance evidence. Flag uncovered or only partially covered requirements.
  3. Check each task has a resolvable purpose, required inputs, produced outputs, completion evidence, and owner/capability where assignment matters.
  4. Build the dependency graph from real input/output or resource dependencies. Reject missing references, cycles, impossible readiness, and unsafe concurrent ownership. Do not reject a forward textual reference merely because its task number is later.
  5. Trace produced artifacts/data into consumers. Flag components created without a planned integration path when integration is required by the outcome.
  6. Check acceptance criteria are observable and capable of falsifying failure.
  7. Check scope against context/risk rather than fixed task/file-count thresholds. Recommend decomposition only when a task cannot preserve necessary context, ownership, or verification quality.
  8. Check architectural boundaries: plans specify required contracts/outcomes while leaving implementation choices to the executor unless the choice is itself a requirement.
  9. Compare the plan with the established impact set and unresolved frontier. Every required impact needs implementation, verification, or an explicit justified exclusion.
  10. Return READY only when no unresolved issue prevents safe execution; otherwise BLOCKED with specific gaps. Preserve non-blocking warnings separately.

For an explicitly unfinished/drafting plan, validate only invariants that are meaningful before completion and label deferred checks rather than treating incompleteness as failure.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Add automated documentation updater to any Claude skill. Creates a Python sync script that downloads upstream docs, processes markdown for AI consumption, and maintains local cache with configurable refresh. Collects template variables, then delegates implementation through 5-phase workflow. Use when adding auto-updating reference documentation to plugins or skills.

The English summary is being prepared. Showing the original description.

Jamie-BitFlight/claude_skills67Updated Oct 18, 2026

SAM-style feature initiation workflow — discovery through codebase analysis, architecture spec, task decomposition, validation, and context manifest. Use when a user asks to add a feature, plan a feature, or convert an idea into an executable SAM plan.

The English summary is being prepared. Showing the original description.

Jamie-BitFlight/claude_skills67Updated Oct 18, 2026

Browser automation for AI agents using the agent-browser CLI and Playwright. Use when navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, logging into sites, or automating any browser task. Triggers on "open a website", "fill out a form", "click a button", "scrape data", "test this web app", "automate browser actions", or any programmatic web interaction request.

The English summary is being prepared. Showing the original description.

Jamie-BitFlight/claude_skills67Updated Oct 18, 2026

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

The English summary is being prepared. Showing the original description.

Jamie-BitFlight/claude_skills67Updated Oct 18, 2026

Runs the description-drift experiment — spawns all Claude Code agents simultaneously to collect self-reported capabilities, then compares them against static frontmatter descriptions to reveal how reliable orchestrator routing based on descriptions actually is. Use when measuring description drift across the agent fleet, re-running the capability collection experiment, analyzing a specific agent's self-reported capabilities, or auditing whether frontmatter descriptions accurately reflect agent behavior.

The English summary is being prepared. Showing the original description.

Jamie-BitFlight/claude_skills67Updated Oct 18, 2026

Create or adapt Claude Code agent definitions. Use when creating an agent, changing subagent configuration, selecting agent scope, or designing a specialized delegation role.

The English summary is being prepared. Showing the original description.

Jamie-BitFlight/claude_skills67Updated Oct 18, 2026

See all skills by Jamie-BitFlight

Report a problem with this skill