spec-manager
Manage specification files for spec-driven development. Use when creating, updating, or deleting spec files. Supports feat, fix, docs, refactor, and chore scopes.
What this skill does
# Spec Manager
Manages specification files in `specs/{scope}/{work-name}.md` for spec-driven development workflow.
## Principles
1. **One spec = one task** (unless frontend + backend work together)
2. **No "before" sections** - Focus only on the final desired state
3. **XML tag format** - Use XML tags for structure (varies by scope)
4. **Minimal code examples** - Avoid code in specs; if necessary, keep it brief and illustrative
5. **Check for duplicates** - Always verify if similar specs exist before creating
## Operations
### Create
1. Analyze request and infer scope (feat/fix/docs/refactor/chore)
2. Search `specs/{scope}/` for similar existing specs
3. If found, ask: "Create new", "Update existing", or "Cancel"
4. If ambiguous scope, ask user to confirm
5. Generate filename (lowercase-with-hyphens)
6. Use appropriate template based on scope
7. Fill in XML tags based on user request
### Update
1. List existing specs in relevant scope
2. Let user select which to update
3. Verify update aligns with original purpose
4. If purpose changed significantly, suggest new spec
5. Apply changes while maintaining XML structure
### Delete
1. List all specs organized by scope
2. Let user select spec(s) to delete
3. Confirm and remove
### List
Display all specs organized by scope directory structure.
## Templates
See templates directory for scope-specific XML tag structures:
- `feat` → [templates/feat-template.md](templates/feat-template.md)
- `fix` → [templates/fix-template.md](templates/fix-template.md)
- `docs` → [templates/docs-template.md](templates/docs-template.md)
- `refactor` → [templates/refactor-template.md](templates/refactor-template.md)
- `chore` → [templates/chore-template.md](templates/chore-template.md)
Each template uses different XML tags appropriate to its scope.
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.