Initialize spec documents (requirements, specs, plans) for a new task. Creates scaffolded markdown files in specs/ directory. Use when user wants to start a new task specification.
Initializes task specification documents and creates a git branch for new projects.
/plugin marketplace add datamaker-kr/synapse-claude-marketplace/plugin install sdd-helper@synapse-marketplaceThis skill is limited to using the following tools:
Part of the spec-manager agent. This skill scaffolds the initial spec documents for a new task.
The user provides a task title as arguments: $ARGUMENTS
Arguments may optionally include a ticket ID prefix. Supported formats:
/init-specs SYN-1234 User Authentication Flow — ticket ID + title/init-specs User Authentication Flow — title only (ticket ID asked later)If no task title is provided, ask the user for a task title before proceeding.
SYN-1234, PROJ-99, #123). If so, extract it as the ticket ID and use the remaining text as the task title.Ticket field in the requirements templateConvert the task title to a URL-friendly slug:
Example: "User Authentication Flow" -> user-authentication-flow
Create and checkout a new git branch for this task:
Build branch name:
{ticket-id}-{slug} (e.g., syn-1234-user-authentication-flow)feat-{slug} (e.g., feat-user-authentication-flow)Check current git state:
git status to check for uncommitted changesCreate and checkout the branch:
git checkout -b {branch-name}git checkout {branch-name})Report: Confirm the branch was created and checked out
Check if a directory already exists at specs/{slug}/. If it does, warn the user and ask whether to overwrite or choose a different title.
Create the specs/{slug}/ directory and the following three files inside it:
specs/{slug}/requirements.md# Requirements: {Original Task Title}
> Created: {YYYY-MM-DD}
> Status: Draft
> Ticket: {ticket-id or "N/A"}
## Overview
<!-- Describe the task/feature at a high level. What problem does it solve? -->
## Goals
<!-- What are the primary goals of this task? -->
- [ ] Goal 1
- [ ] Goal 2
## Functional Requirements
<!-- Describe what the system should DO. Be specific and measurable. -->
### FR-1: {Requirement Name}
- **Description**:
- **Acceptance Criteria**:
- [ ]
### FR-2: {Requirement Name}
- **Description**:
- **Acceptance Criteria**:
- [ ]
## Non-Functional Requirements
<!-- Performance, security, scalability, maintainability, etc. -->
- **Performance**:
- **Security**:
- **Scalability**:
## Constraints
<!-- Technical constraints, time constraints, dependencies, etc. -->
-
## Out of Scope
<!-- Explicitly state what is NOT included in this task -->
-
## References
<!-- Links to related documents, designs, APIs, etc. -->
-
specs/{slug}/specs.md# Specs: {Original Task Title}
> Created: {YYYY-MM-DD}
> Status: Pending (waiting for requirements)
> Requirements: [requirements.md](./requirements.md)
## Overview
<!-- This document will be generated from requirements. Run /specify-with-requirements after completing requirements. -->
## Technical Specifications
<!-- Auto-generated from requirements analysis -->
## Architecture
<!-- Component design, data flow, integrations -->
## API / Interface Design
<!-- Endpoints, function signatures, data models -->
## Error Handling
<!-- Error scenarios and handling strategies -->
## Dependencies
<!-- External and internal dependencies -->
## Open Questions
<!-- Unresolved questions to clarify -->
-
specs/{slug}/plans.md# Plans: {Original Task Title}
> Created: {YYYY-MM-DD}
> Status: Pending (waiting for specs)
> Specs: [specs.md](./specs.md)
## Overview
<!-- This document will be generated from specs. Run /plan-with-specs after specs are finalized. -->
## Implementation Steps
<!-- Auto-generated from specs analysis -->
## Task Breakdown
<!-- Ordered list of implementation tasks -->
## Testing Strategy
<!-- Test plan for verification -->
## Rollback Plan
<!-- How to undo changes if needed -->
## Progress Tracking
| Step | Status | Notes |
|------|--------|-------|
| | | |
After creating all three files, display a summary:
Spec documents initialized for: "{Original Task Title}"
Branch: {branch-name}
Ticket: {ticket-id or "N/A"}
Created files:
- specs/{slug}/requirements.md <- Write your requirements here
- specs/{slug}/specs.md <- Generated after /specify-with-requirements
- specs/{slug}/plans.md <- Generated after /plan-with-specs
Next step: Edit specs/{slug}/requirements.md with your requirements, then run:
/specify-with-requirements {slug}
specs/ directory if it doesn't existSearch, retrieve, and install Agent Skills from the prompts.chat registry using MCP tools. Use when the user asks to find skills, browse skill catalogs, install a skill for Claude, or extend Claude's capabilities with reusable AI agent components.
Activates when the user asks about AI prompts, needs prompt templates, wants to search for prompts, or mentions prompts.chat. Use for discovering, retrieving, and improving prompts.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.