Skills specs-creator

📦

specs-creator

Name: specs-creator
Author: Emz1998

Content revision r1 Safe ⚙️ External commands🔑 Env variables

Create Structured Product and Design Specs

Teams need clear specifications before implementation starts. This skill turns feature requirements into PRD, technical, and UX specs with validation steps.

Supports: Claude Codex Code(CC)

📊 75 Adequate

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "specs-creator" from https://skillstore.io/skills/emz1998-specs-creator.md and its manifest at https://skillstore.io/api/skills/emz1998-specs-creator/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.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/emz1998-specs-creator.md Signed manifest GET /api/skills/emz1998-specs-creator/manifest Signed lockfile GET /api/skills/emz1998-specs-creator/lockfile

Test it

Using "specs-creator". Create a PRD for a team analytics dashboard from the app vision.

Expected outcome:

A PRD is created with goals, personas, user stories, requirements, scope, success metrics, validation status, and a saved file path.

Using "specs-creator". Create technical specs after the PRD is approved.

Expected outcome:

A technical specification is produced with architecture, data models, API plans, security notes, testing strategy, deployment steps, and validation results.

Using "specs-creator". Create UX specs for the feature using the PRD and technical specs.

Expected outcome:

A UX specification is produced with design principles, screens, component states, responsive guidance, accessibility requirements, and motion rules.

Security Audit

Safe

v8 • 7/9/2026 Open versioned report

All static findings were false positives after context review. The warnings match Markdown formatting, validation-script keywords, and template examples rather than shell execution, secret access, reconnaissance, or malware behavior.

Files scanned

3,183

Lines analyzed

Review items

False positives ignored

Risk Factors

⚙️ External commands (11)

scripts/validate-dependencies.py:88 SKILL.md:10-12 SKILL.md:12-16 SKILL.md:16-18 SKILL.md:18-20 SKILL.md:20-30 SKILL.md:30-35 SKILL.md:35-38 SKILL.md:38-43 SKILL.md:43-44 SKILL.md:44-45

🔑 Env variables (4)

templates/tech.md:820 templates/tech.md:821 templates/tech.md:818 templates/tech.md:819

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/emz1998-specs-creator/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/emz1998-specs-creator/security.svg)](https://skillstore.io/skills/emz1998-specs-creator?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/emz1998-specs-creator?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/emz1998-specs-creator/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/emz1998-specs-creator.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

Emz1998. (2026). specs-creator security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/emz1998-specs-creator/audits/8

BibTeX citation

@techreport{emz1998-emz1998-specs-creator-2026,
  author = {Emz1998},
  title = {specs-creator security audit report (audit version 8)},
  institution = {Skillstore},
  year = {2026},
  number = {8},
  url = {https://skillstore.io/skills/emz1998-specs-creator/audits/8},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "specs-creator security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
  - name: "Emz1998"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/emz1998-specs-creator/audits/8"
identifiers:
  - type: other
    value: "skillstore:emz1998-specs-creator:audit:8"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Draft a Product Requirements Document

Turn an existing app vision into a PRD with goals, user stories, scope, and success metrics.

Prepare Technical Planning Docs

Convert approved product requirements into architecture, data model, API, security, testing, and deployment sections.

Define UX Specification Details

Create UX documentation for design principles, screens, responsive behavior, accessibility, and interaction states.

Try These Prompts

Create a PRD

Create a PRD for this feature using the specs-creator workflow. Confirm prerequisites, use the PRD template, validate the result, and report the file location.

Create Technical Specs

Create technical specs from specs/prd.md. Include architecture, data models, APIs, security, testing, deployment, and implementation details.

Create UX Specs

Create UX specs from specs/prd.md and specs/tech-specs.md. Cover design principles, screens, responsive behavior, accessibility, motion, and dark mode.

Validate and Revise Specs

Review the existing PRD, technical specs, and UX specs for dependency order and template compliance. Run validation, revise gaps, and summarize remaining risks.