메뉴
First-time onboarding — asks where you are, then guides you to the right software engineering workflow. No assumptions.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/tranhieutt/software_development_department --skill start명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
Turns real agent failures, repeated prompts, team-specific workflows, and durable project lessons into better SDD skills or memory entries. Use when the user asks to create/update/refine skills, extract reusable lessons, improve skill routing, encode team process, or save patterns for future sessions.
Provides the vendored agent-style v0.3.5 prose rule pack as a portable Claude skill. Use when installing, syncing, applying, or auditing SDD Agent-Style support in another project, or when a style-review workflow needs the bundled rules.
Reviews Markdown prose against the pinned agent-style v0.3.5 rules and optionally writes a polished copy beside the source. Use for specs, ADRs, PR bodies, release notes, and technical docs when prose quality or evidence discipline matters.
SOC 직업 분류 기준
| name | start |
| description | First-time onboarding — asks where you are, then guides you to the right software engineering workflow. No assumptions. |
| argument-hint | [no arguments] |
| user-invocable | true |
| allowed-tools | Read, Glob, Grep, AskUserQuestion |
| effort | 3 |
This skill is the entry point for new users. It does NOT assume you have a project idea, a framework preference, or any prior architecture. It asks first, then routes you to the right software engineering workflow.
Before asking anything, silently gather context so you can tailor your guidance. Do NOT show these results unprompted — they inform your recommendations, not the conversation opener.
Check:
README.md or .claude/docs/technical-preferences.md to see if frameworks are defined.design/architecture/docs/architecture.mdsrc/ (*.ts, *.js, *.py, *.go, *.java, *.rs, *.cpp).prototypes/.production/ or .github/workflows/.Store these findings internally. You will use them to validate the user's self-assessment and to tailor follow-up recommendations.
This is the first thing the user sees. Present these 4 options clearly:
Welcome to the Software Development Department!
Before I suggest anything, I'd like to understand where you're starting from. Where are you at with your software project right now?
A) No idea yet — I don't have a project concept at all. I want to explore and figure out what to build.
B) Vague idea — I have a rough problem to solve or a general app idea (e.g., "a SaaS for HR" or "an internal dashboard") but nothing concrete.
C) Clear concept — I know the core idea — target users, basic features, maybe a pitch sentence — but haven't formalized the architecture yet.
D) Existing work — I already have design docs, prototypes, code, or significant planning done. I want to organize, refactor, or continue the work.
Wait for the user's answer. Do not proceed until they respond.
The user needs creative exploration and problem definition before anything else. Tech stack choice comes later.
/brainstorm does (guided ideation using software engineering frameworks — user needs, core value proposition)/brainstorm open as the next step/brainstorm — discover your product concept/architecture-decision — decide on the tech stack/design-system — decompose the concept into systems/prototype — test the core functionality/sprint-plan — plan the first sprintThe user has a seed but needs help growing it into a product concept.
/brainstorm [their hint] to develop it/brainstorm [hint] — develop the idea into a full concept/architecture-decision — specify the technical stack/design-system — break down the architecture/prototype — build a minimum viable prototype/sprint-plan — plan the development sprintThe user knows what they want to make but hasn't documented the architecture.
/brainstorm to structure the concept into a proper PRD (Product Requirements Document)./architecture-decision./brainstorm or /architecture-decision (their pick)/tech-debt (if reviewing legacy ideas) or /design-system/team-feature — allocate tasks to specialized AI agents/sprint-plan — plan the first sprintThe user has artifacts already. Figure out what exists and what's missing.
/project-stage-detect for a full analysis/architecture-decision should come first/project-stage-detect — full gap analysis/code-review — analyze existing codebase quality/team-feature / /team-backend / /team-frontend — assign specialized agents to specific tasks/sprint-plan — organize the remaining workAfter presenting the recommended path, ask the user which step they'd like to take first. Never auto-run the next skill.
"Would you like to start with [recommended first step], or would you prefer to do something else first?"
When the user chooses their next step, let them invoke the skill themselves
or offer to run it for them. Either way, the /start skill's job is done
once the user has a clear next action.
src/. Did you mean to pick D (existing work)? Or
would you like to start fresh with a new concept?"design/. Want to pick up where
you left off? Try /sprint-plan or just tell me what you'd like to work on."This skill follows the collaborative design principle: