From dt-workspace
Generate workflow documentation from SOW file. Creates organized project documentation with BDD features, API specs, database schemas.
npx claudepluginhub deepaktiwari09/dt-workspace-plugin --plugin dt-workspace[sow-file] [--preset <preset>]# Scaffold Workflow Documentation Generate comprehensive workflow documentation from a Statement of Work (SOW) document. ## Prerequisites - `.dt-workspace` config file must exist (run `/dt-workspace:init` first) - SOW markdown file must exist ## Steps ### 1. Load Configuration Read `.dt-workspace` config file. If not found, instruct user to run init first. ### 2. Determine Settings - SOW file: argument > config.sowPath - Preset: --preset argument > config.defaultPreset > "microservices" - Output: config.outputDirectory > "./workflows" ### 3. Read and Analyze SOW Read the SOW file ...
/scaffoldScaffolds Next.js App Router pages, layouts, server/client components, API routes, server actions, and loading/error states following best practices and project patterns.
/scaffoldScaffolds production-ready project for API, web, CLI, lib, or fullstack using TypeScript, Python, Go, or Rust. Includes src/tests, Docker, GitHub Actions CI/CD, git init, deps, and verification.
/scaffoldDetects .NET project architecture and generates complete feature slices with endpoints, handlers, validators, DTOs, EF configs, and integration tests.
/scaffoldInteractively scaffolds myfy components like modules, routes, providers, tasks, settings, or full features by gathering requirements and generating code.
/scaffoldScaffolds a TypeScript/Node.js project using the Bankr Agent API. Supports bot, web-service, dashboard, or CLI types via project-type argument.
/scaffoldScaffolds a TypeScript/Node.js project using the Bankr x402 SDK. Supports bot, web-service, dashboard, and CLI types with customizable structure and files.
Generate comprehensive workflow documentation from a Statement of Work (SOW) document.
.dt-workspace config file must exist (run /dt-workspace:init first)Read .dt-workspace config file. If not found, instruct user to run init first.
Read the SOW file and extract structured module definitions:
{
"projectName": "From SOW",
"platforms": ["web-application", "mobile-app"],
"modules": [
{
"id": "module-id",
"name": "Module Name",
"platform": "web-application",
"description": "Description",
"features": ["feature-1", "feature-2"],
"services": ["service-name"],
"databases": ["PostgreSQL"],
"kafkaTopics": ["topic.name"],
"websocketEvents": ["event.name"],
"awsServices": ["S3"]
}
]
}
For each platform and module, create:
<output>/
├── README.md # Main index with all modules
├── <platform>/
│ ├── timeline.md # Platform development timeline
│ └── <module-id>/
│ ├── README.md # Module overview
│ ├── user-flows/ # User journey scenarios
│ │ ├── index.md
│ │ └── <feature>.md
│ ├── technical-specs.md
│ ├── api-contracts.md
│ ├── database-schema.md
│ ├── [preset-specific].md # realtime-events, etc.
│ ├── security-specs.md
│ ├── testing-strategy.md
│ ├── error-handling.md
│ └── features/
│ └── <feature>.feature
For each document, generate content based on preset templates with placeholders:
[To be documented] for sections needing AI completionUpdate .dt-workspace with generated paths:
{
"lastGenerated": "<ISO timestamp>",
"generatedPaths": {
"platforms": {
"web-application": {
"path": "./workflows/web-application",
"modules": [
{"id": "module-id", "name": "Module Name", "path": "./workflows/web-application/module-id"}
]
}
}
}
}
GENERATION COMPLETE
Project: <name>
Preset: <preset>
Location: <output>
Modules: X
Files: Y
Directories: Z
Next steps:
1. Review generated files
2. Run /dt-workspace:populate to fill placeholders
3. Update BDD scenarios with specific test cases
Based on selected preset, generate appropriate documents. See skill references for preset details.