drive-create-project
$
npx mdskill add prisma/prisma-next/drive-create-projectCreates transient project workspace structure for immediate shaping.
- Solves starting new projects by scaffolding required directories and stub files
- Depends on file system operations to create folder hierarchies automatically
- Decides scope based on input slug, naming conventions, and user preferences
- Delivers results by generating standard paths for specs, plans, and assets
SKILL.md
.github/skills/drive-create-projectView on GitHub ↗
---
name: drive-create-project
description: >
Create a new transient project workspace under projects/<project>/ (folders + optional stub docs),
then hand off to drive-create-spec / drive-create-plan.
metadata:
version: "2026.3.1"
---
# Create Project Workspace
Create the standard `projects/<project>/` structure so shaping work can start immediately and artifacts land in the right place.
## When to use
Use at the start of every new project. This is the expected first step before writing the project spec and plan.
It’s also useful when a developer wants to:
- Start a new project and needs the `projects/<project>/` directory scaffolded
- Create the canonical spec/plan file locations before shaping begins
- Normalize a proposed project name into a consistent kebab-case slug
## Inputs to collect (minimal)
- `{project}` slug (kebab-case). If the developer provides a name like "Payments Revamp", derive `payments-revamp` and confirm by stating the derived slug (don’t ask them to retype it).
- Whether to create stub files (default: yes)
- Whether to immediately start shaping the project spec (default: yes)
## Output layout (always)
Create (if missing):
- `projects/{project}/`
- `projects/{project}/specs/`
- `projects/{project}/plans/`
- `projects/{project}/assets/`
Notes:
- `projects/{project}/` is **transient**. At close-out: verify acceptance criteria, migrate long-lived docs (incl. ADRs for system changes) into `docs/`, then delete `projects/{project}/`.
- Because `projects/{project}/` is deleted, close-out must also **strip repo-wide references** to transient project docs (e.g. links in `docs/**`, READMEs, scripts) by replacing them with canonical `docs/` links or removing them.
- Project-level artifacts live at the project root:
- Spec: `projects/{project}/spec.md`
- Plan: `projects/{project}/plan.md`
## Stub files (optional)
If stubs are requested (or defaulted) **and** the developer is **not** immediately starting shaping via `drive-create-spec`:
- `projects/{project}/spec.md` (project spec placeholder)
- `projects/{project}/plan.md` (project plan placeholder)
Use these minimal stubs:
### `projects/{project}/spec.md`
```markdown
# Summary
_Drafted via drive-create-spec. Replace this placeholder._
# Description
_Problem, users, scope. Replace this placeholder._
# Requirements
## Functional Requirements
## Non-Functional Requirements
## Non-goals
# Acceptance Criteria
- [ ] _Replace this placeholder_
# References
# Open Questions
```
### `projects/{project}/plan.md`
```markdown
# [Project Plan]
## Summary
_Drafted via drive-create-plan. Replace this placeholder._
**Spec:** `projects/{project}/spec.md`
## Milestones
### Milestone 1: [Name]
**Tasks:**
- [ ] _Replace this placeholder_
## Close-out (required)
- [ ] Verify all acceptance criteria in `projects/{project}/spec.md`
- [ ] Migrate long-lived docs into `docs/`
- [ ] Strip repo-wide references to `projects/{project}/**` (replace with canonical `docs/` links or remove)
- [ ] Delete `projects/{project}/`
```
## Next step (default)
If the developer wants to start shaping now (default), hand off immediately:
- Run `drive-create-spec` targeting `projects/{project}/spec.md`
- Then run `drive-create-plan` targeting `projects/{project}/plan.md`
More from prisma/prisma-next
- adr-review>-
- ast-visitor-pattern>-
- bumping-biomeBumps `biome` package versions (e.g. `@biomejs/biome`) using `pnpm`, aligns `biome.jsonc` files with the new version/s across the repository and runs biome-related checks. Use when required to update `biome` to a newer version - explicitly or implicitly (e.g. after running `pnpm up`, `pnpm update`, `pnpm upgrade` without specific package names).
- contrib-prOpen a high-quality external contributor PR against prisma-next. Use when the user is an outside contributor (not a Prisma maintainer) and wants to submit a change as a pull request from a fork. Encodes the contribution flow from CONTRIBUTING.md so the resulting PR passes review on the first round.
- drive-agent-personasLibrary of agent personas — named bias-frames that other skills load to shift execution-time defaults. Skills name a persona by ID (e.g. "Adopt the architect persona"), and this skill resolves that ID to the persona doc that frames the executor for the rest of the task. Use when authoring a new skill that needs a particular reviewer/implementer/orchestrator stance, or when an existing skill instructs you to adopt a named persona.
- drive-create-plan>
- drive-create-spec>
- drive-discussionDrops the agent into a structured Q&A mode that iterates with the user toward a complete understanding of a topic, then documents the outcome (project spec, plan, decision record, or whatever shape fits). The agent adopts one or more personas from the `drive-agent-personas` library — named explicitly by the user, or inferred from conversation context and announced. Typical use is design work at the start of a task, or mid-implementation when a load-bearing assumption has been falsified. Use ONLY when the user explicitly invokes this skill (e.g. "discussion mode", "pressure-test this", "let's design this", "design mode", "tech design mode", "product mode", "pm mode", "challenge my idea"). Never auto-invoke.
- drive-orchestrate-plan>
- drive-pr-descriptionGenerates PR descriptions by analyzing git diffs between the current branch and the default branch. Use when the user requests a PR description, pull request summary, or commit message for a squash merge.