goal-workflow

Implement specs into working output and verify each requirement with evidence.

2|1|Updated Apr 22, 2026
One-click install
npx skills add https://github.com/pytholic/claude-skills --skill goal-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: goal-workflow
Source: https://github.com/pytholic/claude-skills/tree/main/goal-workflow
Command: npx skills add https://github.com/pytholic/claude-skills --skill goal-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a written spec into a completed implementation, then checks every requirement before reporting back, reducing missed details and unverified changes.

Core Features & Use Cases

  • Spec Parsing: Breaks requirements into discrete, verifiable items.
  • Implementation Guidance: Keeps work focused on the stated scope and avoids unnecessary additions.
  • Parallel Verification: Reviews each requirement independently and summarizes evidence in a report.
  • Use Case: Use it when you want to go from a product or engineering spec to a finished result with a clear pass/fail audit trail.

Quick Start

Use the goal-workflow skill to implement the spec in the attached file and verify each requirement.

Frequently Asked Questions about goal-workflow

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

FAQPage Schema
How do I implement a spec and verify each requirement automatically?

Spec implementation with automated verification works by decomposing a written spec into discrete requirements, guiding the focused implementation to avoid scope creep, and independently validating each item to generate an evidence-based report.

What is requirement decomposition for engineering tasks?

Requirement decomposition breaks a written product spec into discrete, verifiable items. This allows each engineering task to be implemented with focused scope and independently validated through parallel verification against the original requirements.

How do I generate an evidence-based report for spec implementation?

To generate an evidence-based report, use a workflow that runs parallel verification against each discrete requirement after implementation. It reviews every item independently and summarizes validation evidence into a concise pass/fail audit trail.

Can I use this workflow for post-change validation on engineering tasks?

Yes, this workflow supports post-change validation for engineering tasks. It parses structured specs, guides focused implementation of the stated scope, and verifies each requirement independently to reduce missed details and unverified changes.

Does spec implementation workflow support parallel verification of requirements?

Yes, this workflow supports parallel verification. It reviews each discrete requirement independently after implementation, checks the output against the original spec, and summarizes the validation evidence in a concise reporting format.

What are the limitations of automated spec implementation and verification?

The main limitation is that this workflow requires structured spec parsing to function. Without properly decomposed, discrete requirements in the input, it cannot guide focused implementation or produce an accurate evidence-based pass/fail report.