Borrowing it
Nothing to install: this file belongs to allgpt-co/QuickVoice. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/allgpt-co/QuickVoice/main/.claude/skills/gsd/commands/new-project/SKILL.mdgit clone --depth 1 https://github.com/allgpt-co/QuickVoiceWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/allgpt-co/quickvoice/new-project)<a href="https://agentmods.dev/skills/allgpt-co/quickvoice/new-project"><img src="https://agentmods.dev/badge/skills/allgpt-co/quickvoice/new-project.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00028 | $0.02978 |
| Opus 5 | $0.00014 | $0.01489 |
| Sonnet 5 | $0.00006 | $0.00596 |
| Haiku 4.5 | $0.00003 | $0.00298 |
Grade A, and why
gsd:new-project scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GSD New Project
Initialize a new project through unified flow: questioning → research (optional) → requirements → roadmap.
When to Use
Use this command when:
- Starting a new software project from scratch
- Need to gather project context, define requirements, and create roadmap
- Want to use structured project management with GSD
Core Responsibilities
- Setup project structure - Initialize git repo, create .planning/ directory
- Detect brownfield code - Offer to map codebase first if existing code found
- Deep questioning - Extract user vision through collaborative conversation
- Optional domain research - Spawn 4 parallel researchers if needed
- Define requirements - Scope v1 features from table stakes and differentiators
- Create roadmap - Generate phase structure with success criteria
- Initialize STATE.md - Create project memory
Philosophy
Project Initialization is Dream Extraction
You're helping the user discover and articulate what they want to build. This isn't a contract negotiation — it's collaborative thinking.
Be a thinking partner, not an interviewer. Don't interrogate. Collaborate. Don't follow a script.
Start open. Let them dump their mental model. Don't interrupt with structure.
Follow energy. Whatever they emphasized, dig into that.
Process
Phase 1: Setup
MANDATORY FIRST STEP — Execute these checks before ANY user interaction:
- Abort if project exists:
[ -f .planning/PROJECT.md ] && echo "ERROR: Project already initialized. Use /gsd:progress" && exit 1
- Initialize git repo in THIS directory (required even if inside parent repo):
if [ -d .git ] || [ -f .git ]; then
echo "Git repo exists in current directory"
else
git init
echo "Initialized new git repo"
fi
- Detect existing code (brownfield detection):
# Check for code files
CODE_FILES=$(find . -name "*.ts" -o -name "*.js" -o -name "*.py" -o -name "*.go" -o -name "*.rs" -o -name "*.swift" -o -name "*.java" 2>/dev/null | grep -v node_modules | head -20)
HAS_PACKAGE=$([ -f package.json ] || [ -f requirements.txt ] || [ -f Cargo.toml ] || [ -f go.mod ] || [ -f Package.swift ] || [ -f pyproject.toml ] && echo "yes" || echo "no")
HAS_CODEBASE_MAP=$([ -d .planning/codebase ] && echo "yes" || echo "no")
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 7d ago First seen · 275 lines · 28 tokens per session scan A 71b7a3d5c399
gsd:new-project is a skill published in the GitHub repository allgpt-co/QuickVoice (491 stars, last pushed 25d ago), licensed MIT. It adds 28 tokens to every session and 2,978 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
gsd:new-project
Initialize a new project with deep context gathering and PROJECT.md. Creates project structure, requirements, roadmap, and state.
Read, search, and draft email in the connected mailbox (Gmail or Microsoft 365). Use when the user asks about their inbox, wants a message found or summarized, or wants a reply drafted. Sending is gated by a separate, explicitly granted permission — never assume you can send, and never claim a message was sent unless…
knowledge-search
Answer questions from the organization's indexed documents using knowledgesearch, and cite every claim back to a retrieved passage. Use whenever a question is about document content. Covers the search-first rule, answering only from the closed set of returned passages, the Sources list format, and how to tell an empty…
document-comparison
Evaluate several documents against a shared set of criteria — proposals against requirements, contracts against each other, policies against a standard, candidates against a role. Use whenever the answer is a comparison, a ranking, a scoring, or a gap analysis. Covers fixing the criteria before reading, keeping the…
files-search-and-read
Find and read the documents an agent has been granted access to, using pinchyls and pinchyread. Use whenever a question is about the content of a file in the agent's document folders. Covers discovering files before reading them, which formats can actually be extracted, how to point a reader back at a passage, and…
odoo-read
Query and summarize data from a connected Odoo instance with the odoo read tools (describe, count, read, aggregate). Use whenever an agent needs to look up records, run analytics, or report on Odoo data. Covers the mandatory describe-first workflow, id vs defaultcode disambiguation, the domain/aggregate query syntax…