agentic-engineering-agency/specsafe-new
.claude/skills/specsafe-new/SKILL.md
Create a new spec with PRD, tech stack, and rules. Initializes SPEC stage.
$ install --global
skillsauthnpx skillsauth add agentic-engineering-agency/specsafe specsafe-newInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 1, 2026, 9:17 AM57.3s1 file scanned
SKILL.md
- name:
- specsafe-new
- description:
- Create a new spec with PRD, tech stack, and rules. Initializes SPEC stage.
- disable-model-invocation:
- true
Create a new SpecSafe specification (NEW → SPEC stage).
When to use:
- Starting a new feature
- Need to define requirements before coding
- Want to establish tech stack and rules upfront
Input: Feature name or brief description
Steps
-
Validate project state
Check PROJECT_STATE.md exists (run
specsafe initif not). Review current active specs to avoid conflicts. -
Create the spec
specsafe new "<feature-name>"This:
- Generates a new spec file in
specs/active/ - Assigns a unique SPEC-ID (e.g., SPEC-20260211-001)
- Sets status to SPEC stage
- Updates PROJECT_STATE.md
- Generates a new spec file in
-
Initialize PRD structure
Open the new spec file and populate:
- Purpose (WHY): One paragraph explaining why this feature exists
- Scope (WHAT): In scope and out of scope sections
- Tech Stack: Target frameworks, languages, tools
- Rules: Coding standards, constraints, conventions
-
Define initial requirements
Add to Requirements table:
- Functional requirements (what the system must do)
- Non-functional requirements (performance, security)
- Priority levels (P0=must have, P1=should have, P2=nice to have)
-
Show next steps
Display:
- Spec file location
- Current stage (SPEC)
- Next command:
/specsafe:spec <id>to flesh out details
Output
After creation:
- ✅ Spec file created at
specs/active/SPEC-YYYYMMDD-NNN-<feature-name>.md - ✅ Status set to SPEC stage
- ✅ PROJECT_STATE.md updated
- 📋 Prompt: "Edit the spec to add requirements, then run
/specsafe:spec <id>"
Guardrails
- Feature name should be descriptive (kebab-case recommended)
- Check for naming conflicts with existing specs
- Tech stack decisions should reference existing project standards
- Never start coding without a spec in SPEC or later stage
Example
User: /specsafe:new "user-authentication"
→ Creates SPEC-20260211-004-user-authentication.md
→ Status: SPEC
→ Next: /specsafe:spec SPEC-20260211-004
Related Skills
agentic-engineering-agency/.opencode/skills/specsafe-test
development
VerifiedTrustedCommunity
Generate tests from a SpecSafe specification (SPEC → TEST stage).
2SKILL.mdUpdated Mar 31, 2026
agentic-engineering-agency/.opencode/skills/specsafe-status
development
VerifiedTrustedCommunity
Show SpecSafe project status and metrics.
2SKILL.mdUpdated Mar 31, 2026
agentic-engineering-agency/.opencode/skills/specsafe-qa
development
VerifiedTrustedCommunity
Run QA validation (CODE → QA stage).
2SKILL.mdUpdated Mar 31, 2026
agentic-engineering-agency/.opencode/skills/specsafe-new
development
VerifiedTrustedCommunity
Create a new SpecSafe specification using the TDD workflow.
2SKILL.mdUpdated Mar 31, 2026