بنقرة واحدة
tdk-sub-workspace-init
Initialize a new sub-workspace configuration in the current directory
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Initialize a new sub-workspace configuration in the current directory
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
| name | tdk-sub-workspace-init |
| description | Initialize a new sub-workspace configuration in the current directory |
| metadata | {"version":"1.0.0"} |
Create a new .specify.json configuration file for the current sub-workspace.
/sub-workspace.init [sub-workspace-name]
.specify/.specify.json exists → if yes, ask user to overwrite.specify/.specify.yaml exists but .specify.json does NOT:
bash .specify/scripts/bash/migrate-yaml-to-json.sh.specify.jsonMigration failed — migration script not available or manual migration required.
Run: bash .specify/scripts/bash/setup.sh
Then retry: bash .specify/scripts/bash/migrate-yaml-to-json.sh
.specify.jsonInvoke tdk-load-project-context with require_feature_dir: false and require_prefix_validation: false.
If PROJECT_CONTEXT.CONFIG_FOUND is true:
PROJECT_CONTEXT.CONFIG_FOUND is false:Scan current directory for:
| File | Detection |
|---|---|
package.json | language: typescript/javascript |
tsconfig.json | language: typescript |
pyproject.toml | language: python |
go.mod | language: go |
Cargo.toml | language: rust |
Framework detection:
| Pattern | Framework |
|---|---|
next.config.* | nextjs |
vite.config.* | vite |
vue.config.* | vue |
angular.json | angular |
Create .specify/.specify.json:
{
"version": "1.0",
"name": "{sub_workspace_name}",
"type": "sub-workspace",
"docs": {
"path": ".specify/configurations",
"rules": []
},
"metadata": {
"language": "{detected_language}",
"framework": "{detected_framework}",
"packageManager": "{detected_pm}",
"testFramework": ""
},
"rules": [],
"commands": {
"test": "",
"build": "",
"lint": ""
}
}
Use DOCS_PATH from workspace config if available, otherwise default to .specify/configurations:
{DOCS_PATH}/ if not exists{DOCS_PATH}/rules.md from template (use .specify/examples/rules-template.md)Sub-workspace initialized: {sub_workspace_name}
Created:
- .specify/.specify.json
- {DOCS_PATH}/
- {DOCS_PATH}/rules.md
Detected:
- Language: {language}
- Framework: {framework}
Next steps:
1. Edit .specify/.specify.json to configure sub-workspace
2. Edit {DOCS_PATH}/rules.md to add sub-workspace rules
3. Run /sub-workspace.list to verify workspace integration