packbot/create-spec
.claude/skills/create-spec/SKILL.md
Create a feature specification document. Use before implementing complex features to define requirements, API contracts, edge cases, and acceptance criteria.
development
Updated Apr 16, 2026
$ install --global
skillsauthnpx skillsauth add packbot/agentic-coding-boilerplate create-specInstall 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 16, 2026, 9:05 PM4.3s1 file scanned
SKILL.md
- name:
- create-spec
- description:
- Create a feature specification document. Use before implementing complex features to define requirements, API contracts, edge cases, and acceptance criteria.
- disable-model-invocation:
- true
Create Spec: $ARGUMENTS
Create a feature specification for: $ARGUMENTS
Present the completed spec for review before implementation begins.
Steps
- Understand the feature — Ask clarifying questions if the requirements are ambiguous
- Research the codebase — Find related modules, existing patterns, and potential integration points
- Write the spec — Cover all sections below with concrete details
- Identify risks — What could go wrong? What are the unknowns?
- Define acceptance criteria — How do we know the feature is done?
Spec Sections
Summary
One paragraph: what the feature does, what problem it solves, who benefits.
Detailed Design
- Expected behavior (inputs, outputs, side effects)
- API / interface contracts
- Data model changes (if any)
Affected Modules
List every module/file that will be created or modified.
Edge Cases
Null/empty inputs, large inputs, concurrent access, unavailable dependencies.
Security & Performance
Input validation, auth requirements, query efficiency, caching needs.
Acceptance Criteria
Specific, testable conditions that define "done".
Quality Checklist
- [ ] Feature description is clear and unambiguous
- [ ] All affected modules/files are identified
- [ ] API contracts are defined (inputs, outputs, error cases)
- [ ] Edge cases are listed
- [ ] Acceptance criteria are testable
- [ ] Security implications are considered
- [ ] Performance implications are considered
Related Skills
packbot/write-tests
development
VerifiedTrustedCommunity
Write comprehensive tests following the Analyze > Strategy > Implement > Verify workflow. Use when adding tests, improving coverage, or when the user asks to write tests for specific code.
SKILL.mdUpdated Apr 16, 2026
packbot/.claude/skills/review-code
development
VerifiedTrustedCommunity
Review code changes or a GitHub PR
SKILL.mdUpdated Apr 16, 2026
packbot/refactor
development
VerifiedTrustedCommunity
Refactor code safely following the Analyze > Plan > Refactor > Verify workflow. The key rule is that behavior must not change. Use when improving code structure, readability, or modularity.
SKILL.mdUpdated Apr 16, 2026
packbot/push
tools
VerifiedTrustedCommunity
Push commits to remote and optionally create a PR. Use when the user wants to push their changes.
SKILL.mdUpdated Apr 16, 2026