asset-spec

Generate asset and artifact specifications from repository docs and source material.

18|5|Updated Nov 25, 2025
One-click install
npx skills add https://github.com/wsman/MY-DOGE-MICRO --skill asset-spec-wsman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asset-spec
Source: https://github.com/wsman/MY-DOGE-MICRO/tree/main/.agents/skills/asset-spec
Command: npx skills add https://github.com/wsman/MY-DOGE-MICRO --skill asset-spec-wsman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns complex design, architecture, and reference documents into structured, implementation-ready asset and artifact specifications so teams can move forward with less ambiguity.

Core Features & Use Cases

  • Cross-domain spec generation: Supports both game assets and product artifacts, including APIs, CLIs, SDKs, configs, migrations, deployments, packages, docs, and UI deliverables.
  • Source-driven analysis: Reviews the relevant concept docs, ADRs, UX references, and existing manifests to identify what needs to be specified and what already exists.
  • Approval-gated workflow: Produces grouped asset lists, drafts detailed specs, and waits for explicit user approval before writing files or updating manifests.
  • Use Case: A team needs a new API contract, CLI help spec, and deployment checklist; this Skill organizes the source material, drafts each spec consistently, and prepares manifest updates.

Quick Start

Ask the skill to generate a spec for one target, such as an API, CLI, deployment, or game system, and it will review the source docs before drafting the artifact plan.

Frequently Asked Questions about asset-spec

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

FAQPage Schema
How do I generate implementation-ready asset specifications from existing design documents?

You can generate asset specifications by submitting design docs, architecture records, or manifests. The system reviews this source material, identifies required assets, and drafts structured specs for APIs, CLIs, game systems, or deployments.

What is the best way to turn architecture decision records and UX references into structured API and CLI specs?

Turning ADRs and UX references into structured specs requires a source-driven analysis process that identifies deliverables from your docs. It groups assets, drafts detailed API or CLI contracts, and prepares manifest updates.

Can I draft deployment checklists and package specs from repository docs without losing traceability?

Yes, you can draft deployment checklists and package specs from repository docs while maintaining traceability. The workflow includes source-document review, asset identification, and traceable acceptance checks tying every spec to original requirements.

Does the asset spec generation process wait for approval before writing files or updating manifests?

Yes, the asset spec workflow is approval-gated. It produces grouped asset lists and drafts detailed specifications, but waits for explicit user approval before writing any files or updating existing manifests.

How do I create consistent artifact plans for game systems and characters from unstructured source material?

Creating consistent artifact plans for game systems from unstructured material requires a standardized spec generation process. It reviews game design docs, identifies necessary systems or characters, and drafts uniform specifications with acceptance checks.