.claude/skills/arch-plan/SKILL.md
# Architecture Plan Skill **Name:** arch-plan **Triggers:** `/arch-plan`, "design implementation for", "architect this feature" **Version:** 1.0.0 --- ## Purpose Lightweight architectural planning that runs in an isolated subagent context. Returns a structured 350-word plan to the main conversation without polluting it with the dozens of file reads the planner walked through. **This is NOT the canonical interactive planning command.** For interactive planning with CEO approval gates, the pr
npx skillsauth add CleanExpo/CCW-CRM .claude/skills/arch-planInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Name: arch-plan
Triggers: /arch-plan, "design implementation for", "architect this feature"
Version: 1.0.0
Lightweight architectural planning that runs in an isolated subagent context. Returns a structured 350-word plan to the main conversation without polluting it with the dozens of file reads the planner walked through.
This is NOT the canonical interactive planning command. For interactive planning with CEO approval gates, the project's standard plan template, and the full TASK EXECUTION PROTOCOL, use /plan (which exists at .claude/commands/plan.md). This skill is the cheaper, faster, isolated-context version meant for use inside other subagent workflows (e.g., the /implement skill calls arch-plan as its first phase).
/arch-plan <feature description>Dispatches the planning request to an isolated subagent. The subagent uses grep/glob to understand the relevant codebase area, identifies which files need to change, sequences the steps, and returns a structured plan.
Returns to main context (≤350 words):
filepath + 1-line rationale per fileThe plan is read-only — no code is written, no files are modified. The output goes to the main session for CEO approval before any /implement invocation.
Routes to the existing planner.md agent at .claude/agents/planner.md. That agent already produces the project's standard plan template (Objective / Files / Steps / Risks / Breaking Changes). This skill wraps it in a lightweight isolated-context invocation.
Write or Edit under any circumstances.apps/backend/src/api/routes/translations.py (backend pattern) and apps/web/components/auth/login-form.tsx (frontend pattern) where relevant.apps/backend/src/db/demo_models.py, apps/backend/src/api/routes/demo_auth.py, or apps/web/middleware.ts./plan instead (canonical interactive command)/fix instead/research first to understand the codebase.claude/commands/plan.md — canonical interactive planning command (use this for real planning sessions).claude/agents/planner.md — dispatch target.claude/skills/implement/SKILL.md — calls arch-plan as its first phaseMANAGED_AGENTS_v4_FINAL.md — operating protocol that all plans must respectcontent-media
Autonomously uploads CCW HeyGen demo videos to YouTube as Unlisted, collects video IDs, and patches DemoVideoBanner.tsx + video-registry.json. One-time OAuth setup required. Handles resume, retries, and ID propagation.
data-ai
Clear the freeze boundary set by /freeze, allowing edits to all directories again. Use when you want to widen edit scope without ending the session. Use when asked to "unfreeze", "unlock edits", "remove freeze", or "allow all edits". (gstack)
tools
# Spec Interview Skill **Name:** spec-interview **Triggers:** `/spec-interview`, when requirements unclear **Version:** 1.0.0 --- ## Purpose Interviews user to gather complete requirements before planning. --- ## Interview Questions When requirements are unclear, ask: ### 1. Feature Clarity **Question:** "What is this feature supposed to do?" **Why:** Need clear objective ### 2. User Impact **Question:** "Who will use this and why?" **Why:** Understand user needs ### 3. Success Criteri
development
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. Use when asked to "ship", "deploy", "push to main", "create a PR", "merge and push", or "get it deployed". Proactively invoke this skill (do NOT push/PR directly) when the user says code is ready, asks about deploying, wants to push code up, or asks to create a PR. (gstack)