ent-workflow

Guides agents through OpenSpec CLI workflows for proposals, tasks, and spec updates.

Updated Dec 31, 2025
One-click install
npx skills add https://github.com/victorzhuk/go-ent --skill ent-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ent-workflow
Source: https://github.com/victorzhuk/go-ent/tree/main/pkg/skills/ent/ent-workflow
Command: npx skills add https://github.com/victorzhuk/go-ent --skill ent-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines complex development workflows by guiding agents through the OpenSpec CLI for spec-driven development, artifact management, and agent delegation.

Core Features & Use Cases

  • OpenSpec CLI Guidance: Provides clear instructions for using openspec commands to manage proposals, tasks, and specs.
  • Workflow Patterns: Demonstrates efficient patterns for feature development, incremental changes, and spec updates.
  • Agent Delegation: Offers best practices for inter-agent communication, handoffs, and safety checkpoints.
  • Use Case: A developer needs to implement a new feature. This Skill guides them through creating a change, defining requirements in proposal.md, breaking down work into tasks.md, and finally syncing changes back to the main specifications.

Quick Start

Use the ent-workflow skill to create a new change for adding user authentication.

Frequently Asked Questions about ent-workflow

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

FAQPage Schema
How do I manage spec-driven development workflows using the OpenSpec CLI?

Spec-driven development workflows are managed by guiding agents through the OpenSpec CLI to create change proposals, define requirements in proposal.md, break down work into tasks.md, and sync changes back to main specifications.

What is the best way to delegate tasks between agents during feature development?

Agent delegation is handled by providing best practices for inter-agent communication, handoffs, and enforcing safety checkpoints before executing irreversible operations during feature development.

How do I create a new change proposal for a feature in OpenSpec?

Creating a change proposal involves using OpenSpec CLI commands to initialize a change, defining feature requirements in proposal.md, and tracking implementation progress through tasks.md before archiving.

Do I need the OpenSpec CLI installed to use this agent workflow?

Yes, the OpenSpec CLI is required as this workflow relies on its commands to manage proposals, delta specs, tasks, and archiving processes for spec-driven artifact management.

When should I enforce safety checkpoints during artifact management?

Safety checkpoints should be enforced before any irreversible operations, ensuring agent handoffs and spec updates are validated before syncing delta specs or archiving changes.