From dev-flow
Methodology reference for generating implementation specs. Invoked via /df:spec command.
npx claudepluginhub lttr/claude-marketplace --plugin dev-flowThis skill uses the workspace's default tool permissions.
Transform triage output and user decisions into a detailed implementation specification ready for development.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Transform triage output and user decisions into a detailed implementation specification ready for development.
The skill expects one of:
.aiwork/*/triage.md (any task folder).aiwork/*<ticket-id>*/triage.md, or fetch from Azure DevOpsExtract from triage:
Use AskUserQuestion tool to gather decisions. Organize questions into batches of 3-4 max.
Standard question categories:
Mark questions that need team input (can't be answered by assignee alone).
If not already done in triage, use Explore agent to gather:
Output location: If the project defines an .aiwork/ folder protocol (e.g., naming conventions, frontmatter, folder structure), follow that protocol. Otherwise use these defaults:
Write to .aiwork/{date}_{slug}/spec.md
Where:
{date} = current date as YYYY-MM-DD{slug} = with ticket ID: <ticket-id>-<slugified-title>, without: <slugified-title>If a task folder already exists (from triage or otherwise), place spec.md in the same folder.
Use the template from ${CLAUDE_SKILL_DIR}/assets/spec-template.md.
"Where should <component> live after migration?"
Options:
- "<layer-a> (Recommended)" - <rationale>
- "<layer-b>" - <rationale>
- "Keep in current location" - <rationale>
"Should <dependency> be completed first, or included in this task?"
Options:
- "Wait for <ticket>" - Block until dependency completes
- "Include in this task" - Expand scope to include it
- "Parallel work OK" - Proceed independently, coordinate later
"<Technology> approach?"
Options:
- "<Option A> (Recommended)" - <rationale>
- "<Option B>" - <rationale>