coca-spec

Transform user intent into a structured COCA specification.

34|4|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/darknetopencv-alt/autodev --skill coca-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coca-spec
Source: https://github.com/darknetopencv-alt/autodev/tree/main/src/autodev/skills/coca-spec
Command: npx skills add https://github.com/darknetopencv-alt/autodev --skill coca-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps to transform模糊或绿色地带工作为COCA规范,在实施前明确需求。

Core Features & Use Cases

  • COCA Spec Creation: Transforms user intent into a structured COCA spec, including context, outcome, constraints, and assertions.
  • Use Case: Ideal when a task is initially underspecified, ensuring that all stakeholders have a clear understanding of what needs to be built.

Quick Start

Use the coca-spec skill to create a spec for your upcoming feature.

Frequently Asked Questions about coca-spec

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

FAQPage Schema
How do I write a specification for an underspecified feature?

Creating a specification for underspecified features involves structuring project context, expected outcomes, constraints, and assertions to ensure stakeholders share a clear understanding of requirements before development begins.

What is a COCA specification in project planning?

A COCA specification in project planning is a structured framework that defines context, outcome, constraints, and assertions to reduce ambiguity and ensure all stakeholders understand what needs to be built.

How do I define project requirements for greenfield development?

To define project requirements for greenfield development, transform your initial intent into a structured specification that explicitly scopes the context, outcomes, constraints, and assertions of the planned work.

When do I need to use a COCA spec for requirement definition?

You need to use a COCA spec for requirement definition when a task is initially underspecified, ensuring that all stakeholders have a clear understanding of what needs to be built before implementation begins.

What is the best way to reduce ambiguity in project scoping?

The best way to reduce ambiguity in project scoping is to transform user intent into a structured specification, focusing on context, outcomes, constraints, and assertions to align stakeholder understanding.