skills.rest
GodSpeedAI
GodSpeedAIOFFICIAL
Explore all skills by this author →
WebsiteGitHub

sea-generator-first

Enforce generator-first workflows by directing edits to specifications.

1|Updated Oct 1, 2025
Search Tags:#governance#code-generation#spec-first#development-workflow#SEA-Forge#generator-first
One-click install
npx skills add https://github.com/GodSpeedAI/SEA --skill sea-generator-first
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sea-generator-first
Source: https://github.com/GodSpeedAI/SEA/tree/main/.claude/skills/sea-generator-first
Command: npx skills add https://github.com/GodSpeedAI/SEA --skill sea-generator-first

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

SEA-Forge development often risks drift when developers hand-write code instead of deriving it from formal specifications. This skill enforces a generator-first workflow to keep specs as the source of truth and to prevent handwritten implementations in critical code zones.

Core Features & Use Cases

  • Generator-first enforcement: Redirects coding intent to spec-first artifacts and guarantees that generated code is the product of specifications.
  • Guardrails for edits: Prohibits hand-written changes in libs, apps, or generated zones and provides clear options to update specs instead.
  • Workflow integrity: Integrates with the SEA-DSL and SDS pipelines to maintain deterministic outputs and traceability.
  • Use Case: When starting a new feature, a developer refrains from editing code directly and updates the spec instead; the generator produces the implementation.

Quick Start

Initiate a generator-first session by reviewing the relevant spec, then regenerate code from the spec and validate that no hand-written code exists in generated zones.

Frequently Asked Questions about sea-generator-first

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

FAQPage Schema
How do I enforce a spec-first workflow to prevent hand-written code in generated zones?▼

To enforce a spec-first workflow, you must redirect all coding intent to specifications and regenerate code from specs. This prevents hand-written implementations in critical code zones like libs and apps, guaranteeing deterministic generation.

What is generator-first development and how does it maintain workflow integrity?▼

Generator-first development treats specifications as the source of truth. It maintains workflow integrity by integrating with SEA-DSL and SDS pipelines to produce deterministic outputs and ensure traceability, preventing drift from manual edits.

How do I add a new feature or fix a bug without directly editing code in libs or apps?▼

To add a feature or fix a bug without direct edits, you should review the relevant spec and update it instead of touching the code. The generator then produces the updated implementation from the modified spec.

Why does hand-writing changes in generated zones cause drift in SEA-Forge development?▼

Hand-writing changes causes drift because it bypasses the formal specifications, breaking deterministic generation. When developers manually edit implementations in libs or apps, the code no longer matches the spec-first pipeline outputs.

Related Skills

Explore More Software Engineering Skills→
HaydernCenterpointHaydernCenterpoint

spec-driven-development

Draft structured specifications before coding to clarify requirements.

Community
Advanced
NotMyselfNotMyself
30

speckit-updater

Update SpecKit templates and commands while preserving user customizations.

Community
Advanced
GodSpeedAIGodSpeedAI
1

sds-yaml

Author SDS YAML documents mapping to SEA-DSL for domain models and CQRS operations.

Official
Intermediate
KjellKodKjellKod
36

plan-maker

Generate structured implementation plans with acceptance criteria and validation strategies.

Community
Basic