Create Structured Software Specifications
Unclear feature ideas are hard to turn into reviewable engineering work. This skill guides Claude, Codex, or Claude Code through requirements, design, and task breakdown using EARS notation.
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "spec" from https://skillstore.io/skills/clionegohan-spec.md and its manifest at https://skillstore.io/api/skills/clionegohan-spec/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Using "spec". Create a spec for OAuth login with multi-factor authentication.
Expected outcome:
Using "spec". Break down reporting dashboard requirements for implementation planning.
Expected outcome:
The static analyzer flagged Markdown backticks and inline slash command names as Ruby or shell execution. I found no executable Ruby, shell command execution, prompt injection, network access, or secret access in SKILL.md. The skill documents a specification workflow that asks for confirmation before branch or PR actions.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
https://skillstore.io/skills/clionegohan-spec/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/clionegohan-spec?utm_source=security_passport_badge)<a href="https://skillstore.io/skills/clionegohan-spec?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/clionegohan-spec/security.svg" alt="Skillstore security assessment" loading="lazy"></a><iframe src="https://skillstore.io/embed/skills/clionegohan-spec.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Clionegohan. (2026). spec security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/clionegohan-spec/audits/8@techreport{clionegohan-clionegohan-spec-2026,
author = {Clionegohan},
title = {spec security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/clionegohan-spec/audits/8},
note = {Author version unspecified}
}cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "spec security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
- name: "Clionegohan"
date-released: "2026-07-05"
url: "https://skillstore.io/skills/clionegohan-spec/audits/8"
identifiers:
- type: other
value: "skillstore:clionegohan-spec:audit:8"
description: "Skillstore immutable audit report identifier"
Turn a rough feature request into user stories and acceptance criteria before implementation begins.
Break a large feature into EPIC, Story, and Subtask documents with dependencies and review points.
Create a specification package that can support branch creation and a later PR review.
Create a spec for [feature]. Ask clarifying questions before drafting requirements.
Turn these rough requirements into user stories and EARS acceptance criteria: [requirements].
Analyze the existing codebase context for [feature]. Propose design options, tradeoffs, and a task breakdown.
Create an EPIC, Story, and Subtask plan for [feature]. Include dependencies, file previews, and branch or PR approval prompts.
Author
ClionegohanLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
02f077c174c5335e2f5d02ca15e77b70d9543e58
Maintenance freshness
7/18/2026
Usage
5 downloads Β· 169 views
File structure
π SKILL.md
Guide Spec-Driven Implementation
Feature work often drifts beyond approved acceptance criteria. This skill guides Claude, Codex, and Claude Code through AC review, TDD, scope checks, and completion review.
Create Git Workflow Branches
Manual branch naming can slow specification and implementation workflows. This skill guides Claude, Codex, or Claude Code to create consistent spec and impl branches.
Create Review-Ready Pull Requests
Manual PR preparation can miss context, tests, or review focus. This skill builds structured spec and implementation PR drafts for SDD workflows.
Structure AI Development With Specs
by 89jobrien
Complex AI-assisted projects can lose clarity before implementation starts. This skill guides teams through phased specifications, governance, planning, analysis, and task execution.
Manage Requirement Changes Safely
by yunshu0909
Requirement changes often expand across files without clear approval points. This skill gives Claude, Codex, and Claude Code a gated workflow for scope, impact, validation, and documentation.
Enforce Waterfall Phase Gates
by Chemiseblanc
AI coding sessions can skip requirements, design, or testing when pressure rises. This skill keeps work inside a strict waterfall flow with documented gates.
Create Focused Implementation Plans
by sickn33
Multi-step coding work can become vague, large, and hard to verify. This skill helps Claude, Codex, and Claude Code create short plans with clear tasks, order, and checks.
Analyze Codebases for Business Logic
by DoubleslashSE
Existing systems often hide requirements inside code, tests, and configuration. This skill guides structured analysis that turns code observations into clear business documentation.
Route CC-DevFlow Workflows
by Dimon94
Teams lose time choosing the next CC-DevFlow command during complex delivery work. This skill maps project status, phase gates, and user intent to the right Claude, Codex, or Claude Code workflow.