Skip to content
cccskills
FreePublished on GitHub

verify-feature-outcomes

Verify after implementation that a feature achieved its required user/system outcomes. Use for goal-backward post-implementation verification that tests observable behavior rather than merely checking code existence.

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

See how to install

Files included (2)

  • SKILL.md1.2 KB
  • SKILL-GOALS.md266 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Verify Feature Outcomes

Start from the required outcomes, not the implementation.

  1. Resolve the feature goal, acceptance criteria, constraints, and relevant environment.
  2. For each required outcome, identify an observation that would distinguish success from implementation-shaped activity.
  3. Exercise the feature at the highest practical level that observes the promised behavior; use lower-level inspection only where direct execution is unavailable or insufficient.
  4. Verify integration paths and negative/error behavior when they are material to the contract.
  5. Compare observed results with acceptance criteria and record evidence.
  6. Separate VERIFIED outcomes, GAPS_FOUND, and UNVERIFIED outcomes. Never convert unavailable evidence into success.
  7. Report the smallest concrete gap and the evidence needed to close it.

Do not award success because files, functions, tests, or tasks exist. They are evidence only when they demonstrate the required outcome.

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 20, 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 20, 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 20, 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 20, 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 20, 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 20, 2026

See all skills by Jamie-BitFlight

Report a problem with this skill