nsheaps/spec-management
plugins/spec-validation/skills/spec-management/SKILL.md
Manages spec files for requirements capture and validation
$ install --global
skillsauthnpx skillsauth add nsheaps/ai-mktpl spec-managementInstall 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: Jun 7, 2026, 5:59 AM135.1s1 file scanned
SKILL.md
- name:
- spec-management
- description:
- Manages spec files for requirements capture and validation
Spec Management Skill
When Claude Activates This Skill
This skill activates when:
- User requests a new feature or implementation
- User asks to modify existing functionality
- A task requires planning before implementation
- Validation against requirements is needed
What This Skill Enables
1. Requirements Capture
- Extract requirements from user prompts
- Create minimal, focused spec files
- Avoid scope creep and assumptions
2. Spec File Management
- Create specs in
docs/specs/ - Move existing specs to
docs/specs/draft/before updates - Maintain spec version history
3. Implementation Validation
- Verify changes against spec requirements
- Ensure acceptance criteria are met
- Track completion status
How Claude Uses This Skill
New Feature Request
- Use Explore agent to understand codebase
- Use Plan agent to design approach
- Create spec file with user's requirements only
- Commit spec before implementation
- Implement feature
- Validate against spec
- Add unit tests
Updating Existing Feature
- Move existing spec to
docs/specs/draft/ - Create updated spec with new requirements
- Commit spec changes
- Implement changes
- Validate against updated spec
Spec File Format
# Feature Name
## Requirements
- [User's direct requirements]
## Acceptance Criteria
- [Testable conditions]
## Notes
- [Clarifications only]
Best Practices
- Keep specs minimal: Only what user requested
- Commit specs first: Before any implementation
- Validate continuously: Check spec during development
- Test coverage: Unit tests for acceptance criteria
- Don't wait for CI: Push and continue, check later
Requirements
docs/specs/directory existsdocs/specs/draft/directory for archived specs- Git for version control
Limitations
- Specs only capture explicit requirements
- Does not auto-generate tests
- Requires manual validation
Related Skills
nsheaps/github-app-session-env
tools
VerifiedTrustedCommunity
Manually reproduce what the github-app plugin's SessionStart hook does to make a GitHub App installation token usable in the current session — materialize the PEM, generate the token, isolate GH_CONFIG_DIR, write the runtime env file, and wire CLAUDE_ENV_FILE so every Bash call sees GH_TOKEN/GITHUB_TOKEN. Use when the hook did not run, the token is missing from the environment, or a shell/teammate needs the token wired up by hand. <example>GH_TOKEN isn't set even though github-app is configured</example> <example>the github-app SessionStart hook didn't run, set up the token manually</example> <example>wire the github app token into CLAUDE_ENV_FILE</example> <example>gh keeps falling back to the wrong account, isolate GH_CONFIG_DIR</example>
3SKILL.mdUpdated Jun 9, 2026
nsheaps/github-app-git-identity
tools
VerifiedTrustedCommunity
Manually configure the GitHub App bot git identity the way the github-app plugin's SessionStart hook does — resolve the app slug and bot user ID, build the <slug>[bot] name and noreply email, set GIT_AUTHOR_*/GIT_COMMITTER_* env vars, and write an isolated GIT_CONFIG_GLOBAL with the gh auth git-credential helper. Use when commits are attributed to the wrong account, "Author identity unknown" appears, or git identity must be set up by hand. <example>my commits are showing up as the handler, not the bot</example> <example>git says Author identity unknown after the github-app hook ran</example> <example>configure the github app bot git identity manually</example> <example>set up the gh credential helper for git push</example>
3SKILL.mdUpdated Jun 9, 2026
nsheaps/plugins/bash-command-rejection/skills/bash-chaining-alternatives
tools
VerifiedTrustedCommunity
# Bash Chaining Alternatives This skill teaches you how to work around the bash command chaining restriction enforced by this plugin. ## Why Chaining is Blocked The `bash-command-rejection` plugin blocks these operators: | Operator | Name | Why Blocked | | -------- | ---------- | ----------------------------------------------------------------------------------- | | `&&` | AND chain | Runs cmd2 only if cmd1 su
3SKILL.mdUpdated Jun 7, 2026
nsheaps/claude-code
tools
VerifiedTrustedCommunity
Reference material for Claude Code internals — the on-disk layout under ~/.claude and project-scope .claude, the plugin cache, session-env propagation, and the full hook lifecycle. Auto-recall when working on Claude-Code-related tasks: writing or debugging hooks, authoring plugins, inspecting session state, troubleshooting why an env var is or isn't visible to a Bash tool call, or when paths under ~/.claude or ~/.claude/plugins/ come up.
3SKILL.mdUpdated May 6, 2026