How do I install the D Workspace Project skill?

Run npx skillmds@latest add double-sheng/d-workspace-project in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is D Workspace Project safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with D Workspace Project?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is D Workspace Project free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published D Workspace Project?

double-sheng (@double-sheng) published this skill. Their other Agent Skills are listed on their SkillMD profile.

D Workspace Project by double-sheng

Name: D Workspace Project
Rating: 4.2 (5 reviews)
Author: double-sheng

D Workspace Project

Use when Codex needs to create, initialize, scaffold, or manage a new or existing project (project). Triggered when the user says anything about creating a new project, starting a new project, building a project, scaffolding, or when project files need to be organized. Ensures ALL project work follows the D:\Workspace conventions: D:\Workspace\_global-workbench\README.md (global workbench), D:\Workspace\_global-pitfall-log\README.md (pitfall log), and D:\Workspace\_project-sop\README.md (SOP). Also applies when resuming work on an existing D:\Workspace project, or when the user asks why project files are not going to D:\Workspace.

double-sheng Updated Sep 22, 2026

File contents

D: Workspace Project Convention

Rules

1. ALWAYS use D:\Workspace for projects

All project files MUST be placed in D:\Workspace. The current chat session directory (e.g. C:\Users...\new-chat-XXX) is for chat-level work/ and outputs/ only -- never for actual project files.

Before any project work, read D:\Workspace_global-workbench\README.md to confirm the conventions.

2. Naming convention

Follow D:\Workspace_project-sop\README.md strictly:

Folder name: project + 3-digit-number + - + project-name
Example: project002-my-awesome-app
Subdirs: docs/ src/ tests/ work/ outputs/
Project root MUST have README.md and AGENTS.md

3. Start a new project: follow the SOP

Read D:\Workspace_project-sop\README.md
Read D:\Workspace_global-pitfall-log\README.md
Determine the next project number (max existing + 1)
Create the project folder under D:\Workspace with all subdirs
Write README.md and AGENTS.md
Initialize git

4. Pitfall log is the shared memory

Read it before starting any project to avoid known issues.
After solving a new problem, append the solution to the pitfall log so it persists across conversations.

5. Sandbox limitation

Codex cannot write directly to D:\Workspace from the sandbox. Workflow:

Generate files in the writable work/ directory of the current chat session
Use Copy-Item with require_escalated to move them to D:\Workspace
Or inform the user to manually cut/paste if escalation is unavailable

Existing projects on D:\Workspace

project001-silly-card
\u5927\u5468\u5973\u5e1d\u5468\u82e5\u79bb (pre-convention, naming exempt)

---name: d-workspace-projectdescription: Use when Codex needs to create, initialize, scaffold, or manage a new or existing project (project). Triggered when the user says anything about creating a new project, starting a new project, building a project, scaffolding, or when project files need to be organized. Ensures ALL project work follows the D:\Workspace conventions: D:\Workspace\_global-workbench\README.md (global workbench), D:\Workspace\_global-pitfall-log\README.md (pitfall log), and D:\Workspace\_project-sop\README.md (SOP). Also applies when resuming work on an existing D:\Workspace project, or when the user asks why project files are not going to D:\Workspace.---# D: Workspace Project Convention## Rules### 1. ALWAYS use D:\Workspace for projects**All project files MUST be placed in D:\Workspace.**The current chat session directory (e.g. C:\Users\...\new-chat-XXX\) is forchat-level work/ and outputs/ only -- never for actual project files.Before any project work, read D:\Workspace\_global-workbench\README.md toconfirm the conventions.### 2. Naming conventionFollow D:\Workspace\_project-sop\README.md strictly:- Folder name: `project` + `3-digit-number` + `-` + `project-name`- Example: `project002-my-awesome-app`- Subdirs: `docs/ src/ tests/ work/ outputs/`- Project root MUST have `README.md` and `AGENTS.md`### 3. Start a new project: follow the SOP1. Read D:\Workspace\_project-sop\README.md2. Read D:\Workspace\_global-pitfall-log\README.md3. Determine the next project number (max existing + 1)4. Create the project folder under D:\Workspace with all subdirs5. Write README.md and AGENTS.md6. Initialize git### 4. Pitfall log is the shared memory- Read it before starting any project to avoid known issues.- After solving a new problem, append the solution to the pitfall log so it persists across conversations.### 5. Sandbox limitationCodex cannot write directly to D:\Workspace from the sandbox.Workflow:1. Generate files in the writable work/ directory of the current chat session2. Use `Copy-Item` with require\_escalated to move them to D:\Workspace3. Or inform the user to manually cut/paste if escalation is unavailable## Existing projects on D:\Workspace- project001-silly-card- \u5927\u5468\u5973\u5e1d\u5468\u82e5\u79bb (pre-convention, naming exempt)

Frequently asked questions