ifandisalim/new-project
cowork-starter-pack/skills/new-project/SKILL.md
Creates a new project in the workspace with a pre-filled project overview. Trigger this skill whenever the user says "new project", "start a project", "create a project", "I want to work on something new", "add a project", or anything that signals they want to kick off a new project. Always interview the user before creating any files.
tools
Updated Apr 22, 2026
$ install --global
skillsauthnpx skillsauth add ifandisalim/JTI-BrivAI new-projectInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 22, 2026, 10:42 PM313.5s1 file scanned
SKILL.md
- name:
- new-project
- description:
- Creates a new project in the workspace with a pre-filled project overview. Trigger this skill whenever the user says "new project", "start a project", "create a project", "I want to work on something new", "add a project", or anything that signals they want to kick off a new project. Always interview the user before creating any files.
New Project
This skill interviews the user about a new project, creates a folder and project overview, and registers the project in CLAUDE.md so Claude knows about it in future sessions.
Step 1 — Interview the user
Before creating anything, ask these questions in a single conversational message. Don't make it feel like a form — keep it natural:
- Name — What's the project called?
- Goal — What is this project trying to accomplish? (one sentence is fine)
- Why — Why does this project matter to you? What's the real reason you're doing it?
- Tangible Outcomes — What does "done" look like? What will exist when this project is successful?
- Open Problems — Do you already know the main problems you'll need to solve? (totally fine if they don't know yet)
Wait for their answers before doing anything else.
Step 2 — Create the project folder and overview
Once you have their answers, create:
02 Projects/<Project Name>/
└── <Project Name> Overview.md
The overview file is the most important file in any project — it's what Claude reads first every time the project comes up.
Use this exact template:
---
type: problems
date: YYYY-MM-DD
project: <Project Name>
---
## Goal
<their goal answer>
## Why
<their why answer>
## Tangible Outcomes
- <outcome 1>
- <outcome 2>
- <outcome 3>
## Open Problems
<if they gave problems, list them numbered: 1. Problem one>
<if they didn't, write: 1. (to be defined — we'll figure these out as we go)>
Step 3 — Update CLAUDE.md
This step is critical — if you don't do this, the good-morning skill and future sessions won't know this project exists.
Open the CLAUDE.md file in the workspace root. Find the ## Active Projects section. If it still has the placeholder text ("No projects yet"), replace it. Otherwise, add the new project after the existing ones.
Add this block:
### <Project Name>
**Goal:** <their goal>
**Why:** <their why>
**Key file:** `<Project Name> Overview.md`
**Open problems:** <brief list or "to be defined">
Also update the ## Folder Structure section to include the new project folder under 02 Projects/.
Step 4 — Confirm and offer to dive in
Tell the user:
- The project folder and overview are created
- CLAUDE.md has been updated so Claude will remember this project
- Ask: "Want to dive into one of the open problems right now, or save it for later?"
Keep it short — they're ready to work.
Related Skills
ifandisalim/help
testing
VerifiedTrustedCommunity
Shows the user everything Claude can help with in this workspace. Trigger this skill whenever the user says "help", "what can you do?", "what can I say?", "how does this work?", "what are my options?", "I'm lost", "what now?", or seems confused about what to do next. This is especially useful right after setup when a new user doesn't know what's possible.
SKILL.mdUpdated Apr 22, 2026
ifandisalim/good-morning
development
VerifiedTrustedCommunity
Morning orientation that recaps recent work and helps decide what to work on. Trigger this skill whenever the user says "good morning", "morning", "let's get to work", "ready to start", "start my day", "what should I work on?", or anything that signals they're beginning a new work session. Use it proactively — if a user opens with a greeting at the start of a session, run this skill before doing anything else.
SKILL.mdUpdated Apr 22, 2026
ifandisalim/end-of-day
development
VerifiedTrustedCommunity
End-of-day shutdown that logs what was worked on so the next Claude session can pick up where things left off. Trigger this skill whenever the user says "end of day", "wrap up", "we're done", "that's it for today", "log today", "done for the day", "goodnight", "shutdown", or anything that signals they're finishing a work session. If the user seems to be wrapping up, suggest running this before they go.
SKILL.mdUpdated Apr 22, 2026
openclaw/taskflow
tools
VerifiedTrustedCommunity
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
357,764SKILL.mdUpdated Apr 10, 2026