spec

Generate structured delegation specs for Codex or async agents.

11|Updated Dec 18, 2025
One-click install
npx skills add https://github.com/brolag/neural-claude-code --skill spec-brolag
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/brolag/neural-claude-code/tree/main/skills/spec
Command: npx skills add https://github.com/brolag/neural-claude-code --skill spec-brolag

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing clear, structured specifications for complex tasks to delegate to Codex or an async agent, reducing back-and-forth and errors.

Core Features & Use Cases

  • Generates a complete Spec document with sections for project, delegated to, priority, date, context, role, action steps, format, and done criteria.
  • Supports end-to-end delegation workflows by predefining the spec structure and delivery format.
  • Use Case: When a task is too complex for direct execution, you can hand it to an async agent via a formal spec to ensure consistent delivery.

Quick Start

Ask the AI to generate a spec for a complex delegation task and save it to specs/{project}-{task-slug}.md.

Frequently Asked Questions about spec

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

FAQPage Schema
How do I write a specification for delegating complex tasks to an async agent?

To write a specification for delegating complex tasks to an async agent, you need a structured document defining project, delegated-to, priority, date, context, role, actions, format, and done criteria. This ensures consistent autonomous execution and reduces back-and-forth errors.

What is an async agent spec and when do I need one?

An async agent spec is a formalized task structure required when a workflow is too complex for direct execution. You need this specification to trigger Tier 2+ tasks and ensure autonomous agents execute multi-step workflows consistently without continuous manual oversight.

How do I generate a spec file for a Codex delegation workflow?

Generating a spec file for a Codex delegation workflow involves prompting the AI to output a complete specification document. The system automatically structures project context, action steps, and delivery format, saving the final spec to a dedicated specs/ markdown file.

Can I use this spec format for multi-step engineering workflows with autonomous execution?

Yes, this spec format is designed specifically for multi-step engineering workflows requiring autonomous execution. It predefines the delivery format and done criteria, satisfying the requirements needed to successfully delegate complex tasks to Codex or an async agent.

What is the best way to structure a task delegation spec to avoid errors?

The best way to structure a task delegation spec to avoid errors is to enforce a complete template including project, delegated-to, priority, date, context, role, action steps, format, and done criteria. This formal structure minimizes ambiguity for async agents.

Why does my async agent fail to execute complex delegated tasks correctly?

Your async agent fails to execute complex delegated tasks correctly when the specification lacks precise action steps, context, or done criteria. Generating a formal spec document with predefined structure ensures the agent has the exact parameters needed for consistent delivery.