skills.rest
zalman0813
zalman0813COMMUNITY
Explore all skills by this author →
GitHub

init-workflow

Generate immutable gan-harness epic specifications from user intent.

Updated Apr 30, 2026
Search Tags:#workflow automation#epic planning#codebase research#immutability#specification generation
One-click install
npx skills add https://github.com/zalman0813/gan-harness --skill init-workflow-zalman0813
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: init-workflow
Source: https://github.com/zalman0813/gan-harness/tree/main/improver/setup-gan-harness-skills/iteration-1/eval-greenfield-cli/without_skill/outputs/.claude/skills/init-workflow
Command: npx skills add https://github.com/zalman0813/gan-harness --skill init-workflow-zalman0813

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill generates immutable high-level specifications for gan-harness epics, ensuring a clear direction for the coding workflow.

Core Features & Use Cases

  • Immutable Spec Generation: Creates a definitive specification document that can't be altered without explicit approval.
  • User Intent Parsing: Interprets user intent and technical requirements to produce comprehensive specs.
  • Fact-Finding Support: Optionally gathers codebase facts during brownfield epics to inform the spec generation.
  • Use Case: When starting a new epic or transitioning from a planning phase, use this Skill to produce the initial spec document ready for the coding loop.

Quick Start

Execute the init-workflow skill to generate the spec for a new gan-harness epic from user intent.

Frequently Asked Questions about init-workflow

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

FAQPage Schema
How do I generate immutable specifications for epic planning?▼

To generate immutable specifications for epic planning, this Skill parses user intent and optional codebase research to produce a standardized, high-level spec document requiring explicit user confirmation before acceptance.

What is the best way to automate workflow compliance for brownfield epics?▼

Automating workflow compliance for brownfield epics involves optionally gathering codebase facts during spec generation, ensuring the resulting high-level specification aligns with existing project architecture and standardized formats.

Do I need codebase research to start the workflow automation for a new epic?▼

Codebase research is not required to start workflow automation for a new epic. The Skill can generate specifications directly from user intent, though fact-finding is optionally supported for brownfield contexts.

Can I modify a generated specification after it has been accepted?▼

Modifying a generated specification after acceptance is restricted by design. The immutability constraint ensures a definitive direction for the coding workflow, preventing alterations without explicit approval.

How does user confirmation work during specification generation?▼

User confirmation during specification generation requires explicit approval to accept the produced high-level spec document. This ensures the standardized format matches user intent before proceeding to the coding loop stage.

Related Skills

Explore More Software Engineering Skills→
telum-aitelum-ai
2

epic-breakdown

Generate user stories, dependencies, and parallelization opportunities from epic specifications.

Official
Advanced
VeraticusVeraticus

brainstorming

Guide Socratic questioning to create an immutable epic and first subtask.

Community
Basic
zalman0813zalman0813

finalize-workflow

Automate epic finalization in gan-harness by promoting ADRs, merging domain terms, regenerating code maps, and archiving details.

Community
Advanced
dhar174dhar174
1

breakdown-epic-arch

Generate an Epic Architecture Specification with Mermaid diagram and tech stack from a PRD.

Community
Advanced