sc30gsw/sample/harness/next-js-pages/skills/sdd-workflow
sample/harness/next-js-pages/skills/sdd-workflow/SKILL.md
# sdd-workflow — Workflow Status Dashboard ## Slash Command ``` /sdd-workflow [slug] ``` ## Purpose Read-only meta skill. Displays the current state of the SDD workflow — which phases are complete, which is next, and any blockers. Does NOT modify any files. --- ## This Skill is Read-Only `sdd-workflow` never writes to or modifies any file. It only reads spec files and git history to report status. There is no approval gate for this skill. --- ## Usage: Specific Feature ``` /sdd-workflo
$ install --global
skillsauthnpx skillsauth add sc30gsw/claude-code-customes sample/harness/next-js-pages/skills/sdd-workflowInstall 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: May 30, 2026, 5:12 AM22.6s1 file scanned
SKILL.md
sdd-workflow — Workflow Status Dashboard
Slash Command
/sdd-workflow [slug]
Purpose
Read-only meta skill. Displays the current state of the SDD workflow — which phases are complete, which is next, and any blockers. Does NOT modify any files.
This Skill is Read-Only
sdd-workflow never writes to or modifies any file. It only reads spec files and git history to report status. There is no approval gate for this skill.
Usage: Specific Feature
/sdd-workflow <slug>
Reads .claude/specs/<slug>/ and displays the full phase chain with status:
SDD Workflow: <slug>
Mode: standard | auto
Branch: feature/<slug> (12 commits ahead of main)
Phase Chain:
[✅] sdd-init — source-notion.md archived
[✅] sdd-requirements — requirements.md: 5 REQs defined
[✅] sdd-review-requirements — review.md: Requirements Review present
[✅] sdd-design — design.md: 8 sections
[✅] sdd-tasks — tasks.md: 12 TASKs defined
[✅] sdd-review-plan — review.md: Plan Review + Traceability ✅
[🔄] sdd-impl — progress: 3/12 done, TASK-004 in-progress
[⏳] sdd-review — waiting for sdd-impl to complete
[⏳] sdd-pr — waiting
Next action: /sdd-impl <slug> TASK-004 (resume in-progress task)
or: CONFIRM sdd-impl (if paused at a gate)
Status icons:
| Icon | Meaning | | ---- | --------------------- | | ✅ | Phase complete | | 🔄 | Phase in progress | | ⚠️ | Phase has a blocker | | ⏳ | Phase not yet started |
Usage: All Features
/sdd-workflow
Lists all spec directories under .claude/specs/ and shows each feature's current phase:
SDD Workflow Overview
Specs directory: .claude/specs/
slug | current phase | status
-------------------------|----------------|-----------------------------------
user-authentication | sdd-impl | 🔄 3/8 tasks done
mail-group-bulk-delete | sdd-pr | ✅ PR #42 open
supplier-csv-export | sdd-design | ⏳ not started
If .claude/specs/ is empty or does not exist:
No spec directories found under .claude/specs/
Run /sdd-init <slug> to start a new feature.
Phase Detection Logic
Each phase is detected by inspecting files inside .claude/specs/<slug>/. Detection is sequential: if a phase's condition is not met, all subsequent phases show ⏳.
| Phase | Detected When |
| ------------------------- | -------------------------------------------------------------------------------------------- |
| sdd-init | source-notion.md exists OR the <slug> directory itself exists |
| sdd-requirements | requirements.md exists AND contains at least one ## REQ- heading |
| sdd-review-requirements | review.md contains a ## Requirements Review section |
| sdd-design | design.md exists (any non-empty content) |
| sdd-tasks | tasks.md exists AND contains at least one ### TASK- heading |
| sdd-review-plan | review.md contains ## Plan Review AND no unchecked ❌ in its Traceability subsection |
| sdd-impl | progress.md has at least one task marked done |
| sdd-review | review.md contains ## Code Review |
| sdd-pr | progress.md contains a ## PR section with a URL, OR review.md contains a GitHub PR URL |
Progress Metrics (sdd-impl)
When sdd-impl is the current phase, show task completion metrics by parsing progress.md:
[🔄] sdd-impl — progress: 3/12 done (25%), 1 in-progress, 8 pending
In-progress: TASK-004 (Create supplier CSV export hook)
Last completed: TASK-003 (Add export button to supplier table)
Count tasks by status:
done: lines matching— doneor[x]in-progress: lines matching— in-progresspending: lines matching— pendingor[ ]
Blocker Detection
For the currently active or blocked phase, surface known blockers:
| Phase | Blocker Condition | Warning Message |
| ------------ | ------------------------------------------------------------ | ------------------------------------------------------- |
| sdd-impl | review.md has no ## Plan Review section | ⚠️ Run /sdd-review-plan <slug> before implementing |
| sdd-review | progress.md has tasks still pending | ⚠️ N tasks still pending — run /sdd-impl <slug> first |
| sdd-pr | review.md has unchecked - [ ] items under ### CRITICAL | ⚠️ N open CRITICAL issues — resolve before creating PR |
| sdd-pr | review.md has no ## Code Review section | ⚠️ Run /sdd-review <slug> before creating PR |
Blockers appear with ⚠️ next to the phase name and a Blocker: line in the output.
Git Branch Detection
Display the current branch and commit count:
git branch --show-current
git log main...HEAD --oneline | wc -l
Output:
Branch: feature/user-authentication (12 commits ahead of main)
If the current branch does not match the slug:
⚠️ Current branch (feature/other-thing) does not match slug (user-authentication)
Switch to the correct branch before running implementation or review skills.
Full Phase Chain Reference
The complete SDD skill chain in order:
1. sdd-init — Archive Notion source, create spec directory
2. sdd-requirements — Write requirements.md from source-notion.md
3. sdd-review-requirements — Review requirements, append to review.md
4. sdd-design — Write design.md (architecture, components, API)
5. sdd-tasks — Write tasks.md (TASK-xxx breakdown)
6. sdd-review-plan — Review plan, verify traceability, append to review.md
7. sdd-impl — TDD implementation, one commit per task
8. sdd-review — Code + security review, append to review.md
9. sdd-pr — Create GitHub PR with traceability and test plan
Example: Fully Complete Feature
SDD Workflow: user-authentication
Mode: auto
Branch: feature/user-authentication (12 commits ahead of main)
Phase Chain:
[✅] sdd-init — source-notion.md archived
[✅] sdd-requirements — requirements.md: 5 REQs (REQ-001 through REQ-005)
[✅] sdd-review-requirements — review.md: Requirements Review present
[✅] sdd-design — design.md: 6 sections
[✅] sdd-tasks — tasks.md: 12 TASKs defined
[✅] sdd-review-plan — review.md: Plan Review, Traceability ✅
[✅] sdd-impl — progress: 12/12 done
[✅] sdd-review — review.md: Code Review (2026-05-26), 0 CRITICAL, 2 HIGH open
[⏳] sdd-pr — waiting
Next action: /sdd-pr user-authentication
Related Skills
sc30gsw/skill-creator
tools
VerifiedTrustedCommunity
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
10SKILL.mdUpdated May 30, 2026
sc30gsw/skills/sdd-workflow
testing
VerifiedTrustedCommunity
# sdd-workflow — Workflow Status Dashboard ## Slash Command ``` /sdd-workflow [slug] ``` ## Purpose Read-only meta skill. Displays the current state of the SDD workflow — which phases are complete, which is next, and any blockers. Does NOT modify any files. --- ## This Skill is Read-Only `sdd-workflow` never writes to or modifies any file. It only reads spec files and git history to report status. There is no approval gate for this skill. --- ## Usage: Specific Feature ``` /sdd-workflo
10SKILL.mdUpdated May 30, 2026
sc30gsw/skills/sdd-tasks
content-media
VerifiedTrustedCommunity
# sdd-tasks **Slash command**: `/sdd-tasks <slug>` **Purpose**: Generate `tasks.md` (TASK-001..N) and `progress.md` from `requirements.md` and `design.md`. --- ## Prerequisites - `.claude/specs/<slug>/requirements.md` must exist - `.claude/specs/<slug>/design.md` must exist (run `/sdd-design` first) --- ## Steps ### 1. Read spec inputs ``` .claude/specs/<slug>/requirements.md .claude/specs/<slug>/design.md ``` Extract: - Every REQ-XXX ID with its acceptance criteria - Every design sect
10SKILL.mdUpdated May 30, 2026
sc30gsw/skills/sdd-review
development
VerifiedTrustedCommunity
# sdd-review — Post-Implementation Code Review ## Slash Command ``` /sdd-review <slug> ``` ## Purpose Run code review and security review on all changes introduced by the feature branch. Append structured findings to `review.md`. Does NOT auto-apply fixes — only proposes them. --- ## Prerequisites - `sdd-impl` has completed: all tasks in `progress.md` are `done` (or at least one is `done`; partial reviews are allowed). - The feature branch must have at least one commit ahead of `main`. -
10SKILL.mdUpdated May 30, 2026