القائمة
Create a brand-new GitHub repo, clone it, and register it in squadrant. Handles both new workspace (new group) and existing workspace (join existing group).
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | squadrant-new-project |
| description | Create a brand-new GitHub repo, clone it, and register it in squadrant. Handles both new workspace (new group) and existing workspace (join existing group). |
Use when the project does not exist yet — you need to create the GitHub repo, clone it locally, and wire it into squadrant.
You need:
my-project)Quantum3-Labs or your GitHub username)public or private/Users/you/Q3/MyGroup/)New workspace (no existing group):
primary automatically.--group-role needed.Existing workspace (joining an existing group):
squadrant projects list to see current groups."landing page", "mobile client", "CLI tool")."primary" — that slot is already taken.gh repo create <org>/<repo-name> --[public|private] --clone --clone-dir <parent-dir>
This creates the repo on GitHub and clones it into <parent-dir>/<repo-name>.
If the repo should start with a README and first commit:
cd <parent-dir>/<repo-name>
echo "# <repo-name>" > README.md
git add README.md
git commit -m "chore: initial commit"
git push
Skip if the repo already has content or the user wants to scaffold separately.
squadrant projects add <repo-name> <parent-dir>/<repo-name> \
--captain "⚓ <repo-name>-captain" \
[--group <group-name>] \
[--group-role "<role description>"]
Omit --group and --group-role for a standalone project with no group.
squadrant projects list
Confirm the new entry appears with the correct path, group, and role.
Complete captain playbook — session startup, crew spawning, status writing, group awareness, and learnings. Use this skill at session start and reference it throughout.
Set up and manage the squadrant↔Telegram integration — bot setup, remote control, command-menu registration, and per-project notification tuning (mute, crew tiers, cap). Use when the user asks about Telegram setup, "why don't commands work", registering the /command menu, or muting/tuning notifications.
Add, edit, or remove a leveled crew routing rule in config.json without hand-editing JSON. Routing rules map task-text keywords to a tier → {agent, model}.
Command playbook — invoked on-demand by `squadrant command [--task ...]`. Covers daily briefing, delegation workflow, project registration, status checking, and learnings review. Command is no longer always-on.
Reconcile squadrant config drift that needs human judgment — changed defaults and invalid values surfaced by `squadrant config check`. Use when the drift banner says "items need review" or the user asks to fix config drift.
Four coding principles derived from Andrej Karpathy's observations on LLM pitfalls. Use to reduce wrong assumptions, overengineering, drive-by refactors, and vague execution. Apply to every crew coding task and every captain review.