veda-spec-execution

Standardize product specification preparation, handoff, and execution workflows.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/VedaAstro/veda-skills --skill veda-spec-execution
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: veda-spec-execution
Source: https://github.com/VedaAstro/veda-skills/tree/main/veda-spec-execution
Command: npx skills add https://github.com/VedaAstro/veda-skills --skill veda-spec-execution

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill turns specification work into a controlled lifecycle, so you can move from research to handoff to execution without losing context, skipping checks, or overcomplicating the first draft.

Core Features & Use Cases

  • Spec Preparation: Draft lean SPEC files with clear scope, required sections, and stop conditions.
  • Handoff Workflow: Generate copy-ready handoff prompts for a fresh session with model, effort, context, and file guidance.
  • Execution Guardrails: Follow the prescribed order, run audits and drift checks, and verify each stage with build steps and structured reports.
  • Use Case: You need to continue a large implementation across sessions and want the next run to pick up exactly where the last one ended, with the right context and reporting format.

Quick Start

Use the veda-spec-execution skill to prepare a SPEC file, hand off the work to a new session, or execute an existing spec with the required checks and report format.

Frequently Asked Questions about veda-spec-execution

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

FAQPage Schema
How do I hand off a spec to a new session without losing context?

Spec execution workflow standardizes transferring work to a new session by generating copy-ready handoff prompts. These prompts include model, effort, context, and file guidance so the next run picks up exactly where the last ended.

What is a spec drift check and when do I need to run it?

A spec drift check is a pre-execution audit that verifies implementation alignment. You need to run it during stage-by-stage builds to ensure the code matches the prescribed scope and required sections before moving to build verification.

How to prepare a SPEC file for implementation with minimal scoping?

Draft a lean SPEC file by defining clear scope, required sections, and stop conditions. This approach requires minimal first-iteration scoping to establish boundaries, preventing you from overcomplicating the initial draft before execution begins.

Does this spec execution workflow support stage-by-stage build verification?

Yes, the spec execution workflow enforces stage-by-stage build verification. It applies execution guardrails that require running audits, drift checks, and structured reports across code, build, and verification steps in a prescribed order.

What's the best way to standardize product specification execution across code and build steps?

The best way to standardize product specification execution is applying a controlled lifecycle workflow. This enforces model-and-effort selection, pre-execution audits, and structured reporting to move from research to handoff without skipping checks.