tdk

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

Primary implementation skill. Execute phases from plan.md ## Phases table. Read plan.md as source of truth for status + dependency graph.

Execute the implementation planning workflow using the plan template to generate design artifacts.

Create spec.md from a feature or child-slice description, or replay --interview against existing spec.md. Supports --fast, memory, and an embedded quality gate.

Project-level architecture recommendation and brownfield recovery advisor. Writes architecture reports only; does not mutate layout or config.

Deprecated compatibility route for /tdk-workspace-layout-propose.

Observe-first onboarding for existing repositories. Summarizes repo shape, current TDK config state, and safe next-step recommendations without product discovery or source-tree changes.

Compare Workspace and Sub-Workspace Docs.

Generate or update the Document Manager index for workspace and sub-workspace docs.

Synchronize documentation files between workspace and sub-workspaces.

Create or update the project constitution and constitution-owned project knowledge artifacts from interactive or provided principle inputs

New-project intake and routing entry point that asks project-inception questions, writes project-inception.md, and recommends safe next TDK routes

Deprecated compatibility route for /tdk-workspace-dependency-policy.

Init or update arc42-lite documentation for one or all configured sub-workspaces. Writes README, architecture, interfaces, and engineering docs under <docsPath>/sub-workspaces/<name>/.

Initialize a new sub-workspace configuration in the current directory

List all sub-workspaces in the current workspace

Interactively review and apply guarded .specify/.specify.json changes derived from workspace layout proposal JSON.

Optional workspace dependency policy workflow. Turns approved layout evidence into reviewable dependency guidance and non-applied enforcement snippets.

Project-level workspace boundary proposal workflow. Writes workspace layout proposal markdown and JSON without mutating runtime config.

Create or update retrospective feedback after a TDK spec: reviews, phase drift, UT results, Langfuse traces when available, and user feedback. Writes retro-feedback.md and supports adding or removing user feedback entries across repeated collection runs.

Load project configuration and resolve feature directory from validated TASK_ID. Called by: tdk-analyze, tdk-clarify, tdk-implement, tdk-plan, tdk-specify (supports --fast mode). NOT user-invocable.

Validate and normalize task ID from $ARGUMENTS or conversation context. Called by: tdk-analyze, tdk-clarify, tdk-implement, tdk-plan, tdk-specify (supports --fast mode). NOT user-invocable.

Create spec.md from a feature or child-slice description, or replay --interview against existing spec.md. Supports --fast, memory, and an embedded quality gate.

Create or update retrospective feedback after a TDK spec: reviews, phase drift, UT results, Langfuse traces when available, and user feedback. Writes retro-feedback.md and supports adding or removing user feedback entries across repeated collection runs.

Load project configuration and resolve feature directory from validated TASK_ID. Called by: tdk-analyze, tdk-clarify, tdk-implement, tdk-plan, tdk-specify (supports --fast mode). NOT user-invocable.

Validate and normalize task ID from $ARGUMENTS or conversation context. Called by: tdk-analyze, tdk-clarify, tdk-implement, tdk-plan, tdk-specify (supports --fast mode). NOT user-invocable.

EPIC-ONLY v1 discovery entry point that creates context-only problem, persona, MVP, and discovery manifest artifacts before tdk-epic-prd, or interviews existing discovery artifacts with --interview

Turn epic PRD artifacts into parent high-level design context before /tdk-task-breakdown. Use after /tdk-epic-prd; child specs do not run HLD by default.

EPIC-ONLY product alignment and slice-map step after tdk-discovery; writes tracker-neutral epic PRD artifacts without minting requirements

Generate parent epic child-spec-seed breakdown artifacts from epic PRD plus /tdk-epic-hld context. Use before child /tdk-specify loops.

Interactive setup guide for TDK environment. Checks prerequisites, verifies config, troubleshoots issues. Use when asking 'how to set up', 'setup help', 'verify setup', 'check prerequisites', 'tdk setup', 'installation guide', 'troubleshoot setup'.

Interactive guide for TDK skills and commands. Shows usage, scenarios, tips, and skill discovery. Use when asking 'how to use /tdk-*', 'what skills are available', 'show scenario', 'find a skill for X', 'tdk guide', 'tdk help'.

This skill should be used when the user asks to 'sync skill docs', 'update docs for new skill', 'check skill documentation', 'verify skill docs are up to date', 'tdk-skill-docs-sync', 'docs sync after skill creation', or needs to scan and update guide documentation (tdk-skills-guide, index, scenarios, document-flow) after creating or modifying a skill in the tdk-speckit marketplace.

Initialize, inspect, check, diff, register, verify, and optimize plan-skill-routing.md through the deterministic TDK routing helper.

Generate Keep-a-Changelog entries for .specify/, .claude/, .github/ config changes. Use when updating commands, scripts, templates, or governance files.

Read approved automation recommendation markdown and scaffold SKILL.md, references stubs, agent.md files, and reviewable routing proposal artifacts.

Recommend skills and agents for one selected sub-workspace from arc42-lite docs, dependency policy, official docs, local installed skill catalog, and direct community skill lookup.

Review or update TDK source guide docs with the accepted Progressive Workflow Guide format using `projects/tdk/.specify/docs/en/guides/index.md` as the route-map source of truth. Use when editing or auditing TDK guides, restructuring guide IA, creating route maps or scenario pages, scanning routed subfiles, checking guide links, or validating docs after an agent updated TDK guides. Default to check-only unless the user explicitly asks to patch docs.

Brainstorm solutions with trade-off analysis and brutal honesty. Use for ideation, architecture decisions, technical debates, feature exploration, feasibility assessment, design discussions.

Advanced knowledge management for Obsidian vaults.Use when: creating/editing .md notes, .canvas visual maps, .base database views, researching existing docs, or validating content consistency.