Directory To Spec
Create a spec directory with specification files per major feature for code in the current directory and its subdirectories.
Install
$ agentstack add skill-tomzx-agents-directory-to-spec ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-tomzx-agents-directory-to-spec) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Convert Directory to Spec
Analyzes code in the current directory and generates a spec/ directory containing one specification file per major feature, each with MUST/SHOULD/MAY requirements.
Prerequisites
- Read access to the current directory and its subdirectories
- A codebase with identifiable features or modules
Steps
- Read and analyze the code in the current directory and subdirectories to identify major features.
- Create the
spec/directory. - For each major feature, create a descriptively named specification file (e.g.,
authentication.md). - Each file must include a
requirementssection using RFC 2119 language (MUST,SHOULD,MAY). - Specifications must remain technology-agnostic: no specific library, framework, or technology choices should appear in the requirements, unless used as illustrative examples (e.g., "the system MUST provide a key-value cache, such as Redis").
Naming rules:
- Use descriptive, lowercase names:
authentication.md - Do NOT number files: ~~
01-authentication.md~~ - Do NOT suffix with
-spec: ~~authentication-spec.md~~
Example Usage
Scenario 1: REST API project Working directory contains auth/, orders/, payments/. Produces:
spec/authentication.mdspec/order-management.mdspec/payment-processing.md
Scenario 2: Single-module library Working directory contains a single Python library with multiple classes. Produces one spec file per major class or responsibility area.
Scenario 3: Frontend application Working directory contains React components. Produces spec files organized around user-facing features rather than individual component names.
Useful Commands Reference
| Command | Description | |---|---| | mkdir spec | Create the spec output directory |
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: tomzx
- Source: tomzx/agents
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.