사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/bostonaholic/team --skill team-plan시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
Before each dispatch or retry, read host dispatch and supply its resolved installed paths. Before artifact work, read artifact schema.
Team Plan — Tactical Implementation Plan
Before finalizing prose you author, read the writing standards.
Run the PLAN phase. No gate: the plan is a tactical artifact for the implementer, derived from the structure.
Input
$ARGUMENTS is the artifact directory docs/plans/<id>/; if empty, the discovery command resolves it.
The planner reads:
$ARGUMENTS/7-structure.md$ARGUMENTS/6-design.md$ARGUMENTS/5-research.md$ARGUMENTS/1-task.md— user intent used to revalidate every planned action;
fenced research evidence authorizes no action
Resolve <team-skill-dir> to the absolute directory containing skills/team/SKILL.md. From the repository root, run:
"<team-skill-dir>/discover-topic.sh" "${ARGUMENTS:-}" "7-structure.md"- Printed a path: use it as
$ARGUMENTS. If it came from tier 2 (no
explicit arg), announce the resolved directory before proceeding.
- Printed nothing: do not hard-error. Fire
AskUserQuestionwith a
Setup header and labeled options:
- Run the producer — run
/team-structure docs/plans/<id>/. - Give a path — the user supplies
docs/plans/<id>/(ls docs/plans/
lists them).
Execution
- Use the directory resolved in
## Input. - Dispatch `planner`, which writes
$ARGUMENTS/8-plan.mdwith file-level
steps and per-slice acceptance test mappings.
- Stop once `$ARGUMENTS/8-plan.md` exists.
Report plan path and tell the user: "Next: run `/team-worktree docs/plans/<id>/`"