create-specification — community create-specification, kuniumi, community, ide skills

v1.0.0
GitHub

About this Skill

Ideal for Development Agents requiring automated documentation generation and project status tracking. Create a structured specification document from user ideas and requirements. Use when the user wants to create a spec, write a specification, document requirements, or start a new feature design.

axsh axsh
[0]
[0]
Updated: 2/25/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Locale and body language aligned
Review Score
7/11
Quality Score
29
Canonical Locale
en
Detected Body Locale
en

Ideal for Development Agents requiring automated documentation generation and project status tracking. Create a structured specification document from user ideas and requirements. Use when the user wants to create a spec, write a specification, document requirements, or start a new feature design.

Core Value

Empowers agents to create structured specification documents in Markdown format, utilizing shell scripts like show_current_status.sh for dynamic status checks and output location determination, and supports JSON output for seamless integration.

Ideal Agent Persona

Ideal for Development Agents requiring automated documentation generation and project status tracking.

↓ Capabilities Granted for create-specification

Automating specification document generation
Determining output locations based on project phase and branch
Extracting project status information using JSON output

! Prerequisites & Limits

  • Requires execution of shell scripts like show_current_status.sh
  • Dependent on specific directory structure and file naming conventions

Why this page is reference-only

  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team handoff, approvals, and repeatable execution, move into workflow collections.
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is create-specification?

Ideal for Development Agents requiring automated documentation generation and project status tracking. Create a structured specification document from user ideas and requirements. Use when the user wants to create a spec, write a specification, document requirements, or start a new feature design.

How do I install create-specification?

Run the command: npx killer-skills add axsh/kuniumi. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for create-specification?

Key use cases include: Automating specification document generation, Determining output locations based on project phase and branch, Extracting project status information using JSON output.

Which IDEs are compatible with create-specification?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for create-specification?

Requires execution of shell scripts like show_current_status.sh. Dependent on specific directory structure and file naming conventions.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add axsh/kuniumi. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use create-specification immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

create-specification

Install create-specification, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Create Specification Workflow

This skill creates a structured specification document (.../ideas/.../XXX-{Name}.md) from user-provided ideas and requirements.

1. Preparation: Check Status and Context

  1. Get status:
    • Run scripts/utils/show_current_status.sh.
    • Extract phase, branch, next_idea_id from the JSON output.
    • Refer to these as [Phase], [Branch], [NextID] below.

2. Determine Output Location

  1. Directory:
    • Base path: prompts/phases/[Phase]/ideas/[Branch]/
    • Example: prompts/phases/001-webservices/ideas/main/
    • Create the directory if it does not exist.
  2. File name:
    • Format: [NextID]-[Name].md
    • [Name] should be a concise label that describes the spec (e.g. Tokenizer, RateLimit-GlobalManagement).

3. Specification Content Structure

The specification must include at least the following sections:

  1. Background: Why this feature or change is needed. Current problems or challenges. May be omitted if unknown.
  2. Requirements: Features to implement and conditions to satisfy. Concrete behaviors and constraints. Clearly distinguish mandatory vs optional requirements.
  3. Implementation Approach: Technologies and architecture to use. Overview of major components/modules. Key design decisions.
  4. Verification Scenarios:
    • IMPORTANT (Preserve Details): If the user provides specific steps, conditions, or test scenarios (e.g. "(1) do X then (2) do Y"), transcribe them here at full granularity. Do NOT summarize or fold them into "Requirements".
    • This section shares the concrete image of "what constitutes done".
    • Recommended format: numbered chronological lists.
  5. Testing for the Requirements:
    • Describe automated verification steps for each requirement.
    • IMPORTANT (Mandatory Automated Verification): Manual-only plans ("visually confirm the screen") are NOT allowed. Always specify verification commands using project-standard scripts:
      • scripts/process/build.sh
      • scripts/process/integration_test.sh
    • Map each requirement to the script/test case that verifies it.

4. Create and Save

  1. User dialogue: Listen carefully, ask clarifying questions. Organize information along the four axes: Background, Requirements, Implementation Approach, and Verification Scenarios.
    • WARNING: If the user provides concrete steps (Scenarios), do NOT silently convert them into abstract "functional requirements" and discard the steps. Always preserve them under "Verification Scenarios".
  2. Markdown formatting: Use headings, lists, tables, code blocks, and optionally Mermaid diagrams.
  3. Save the file to the determined directory.

5. Completion Check

  1. Review: Confirm the spec covers Background, Requirements, and Implementation Approach.
  2. Present file path: Show the user a link to the created file.
  3. Suggest next step: Propose creating an implementation plan if appropriate (but do NOT proceed without explicit user instruction).

Related Skills

Looking for an alternative to create-specification or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

★ 333.8k
⑂ 0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

The React Framework

★ 138.4k
⑂ 0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

★ 98.6k
⑂ 0
Developer