skills.rest
saranskumar
saranskumarCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

gsd-execute

Create a finalized SPEC file and execute the PLAN, EXECUTE, VERIFY, COMMIT workflow.

Updated Apr 19, 2026
Search Tags:#workflow#verification#spec-first#commit-tracking#gsd#code-delivery
One-click install
npx skills add https://github.com/saranskumar/anti-slop --skill gsd-execute-saranskumar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-execute
Source: https://github.com/saranskumar/anti-slop/tree/main/archive/skills-legacy/gsd-execute
Command: npx skills add https://github.com/saranskumar/anti-slop --skill gsd-execute-saranskumar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

SPEC → PLAN → EXECUTE → VERIFY → COMMIT. Before writing code, a finalized SPEC must exist, ensuring atomic commits and empirical proof of completion to prevent vague or partial work.

Core Features & Use Cases

  • SPEC-first workflow: guarantees a finalized spec before implementation.
  • Wave-based PLAN: decomposes work into independent, auditable tasks.
  • EXECUTE protocol: uses structured task formats and deterministic execution.
  • VERIFY and COMMIT: empirical validation and one-commit traceability for each task.
  • Use Case: teams shipping features with strong guardrails and auditable history.

Quick Start

Create a finalized SPEC at .gsd/SPEC.md and then execute the workflow: PLAN → EXECUTE → VERIFY → COMMIT.

Frequently Asked Questions about gsd-execute

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

FAQPage Schema
What is a spec-first software delivery workflow?▼

A spec-first workflow mandates a finalized SPEC document before any coding begins, ensuring every development phase produces verifiable results and preventing partial implementations.

How do I enforce one-commit-per-task discipline in my development process?▼

You can enforce one-commit-per-task discipline by following a wave-based workflow that executes structured tasks, verifies them empirically, and commits each individually to maintain auditable history.

What's the best way to decompose software features into auditable tasks?▼

The best way to decompose features into auditable tasks is using a wave-based PLAN phase, which breaks down the finalized spec into independent, verifiable units matching defined acceptance criteria.

Do I need a finalized spec before starting the execute phase?▼

Yes, a finalized spec at .gsd/SPEC.md is strictly required before executing code, serving as the foundation for deterministic execution and empirical validation against acceptance criteria.

How does empirical verification work in a commit-tracking workflow?▼

Empirical verification validates each completed task against defined acceptance criteria using objective proofs, ensuring the one-commit-per-task traceability accurately reflects finalized, working functionality.

Related Skills

Explore More Software Engineering Skills→
refactory-langrefactory-lang

speckit-baseline

Generate baseline project documentation by executing a script to capture project state.

Official
Intermediate
jholhewresjholhewres
3

dora-metrics

Calculate DORA metrics from git history and deployment logs.

Community
Intermediate
Siamese001Siamese001

pytest-integrity

Validate pytest collection and execution counts to prevent silent test deselection.

Community
Intermediate
auldsyababuaauldsyababua
6

cicd-pipeline-generator

Generate CI/CD pipeline configurations for GitHub Actions, GitLab CI, CircleCI, and Jenkins.

Community
Advanced