SuperAPI AI Directory
Partner中文AI newsFavorites
Skillspeach-intake

peach-intake

Coding & development

View repository

Updated 10-15 21:50

About this skill

Peach Intake

Classifies PeachSolution development requests before actual implementation and determines the next execution path.

Role

peach-intakeis not an implementation skill but a decision gateIt reads the user's natural language request, PRD, existing documents, and the presence of Spec/proto/schema, and determines which criteria should be reinforced first.

This skill performs the following.

  • Determines the task type and scale.
  • Determines whether Spec, DB, and ui-proto are needed.
  • Separates whether development can proceed immediately or criteria need reinforcement.
  • Suggests the order of subsequent skill calls.
  • Reports blocking items as *_REQUIRED.

This skill does not do the following.

  • Code implementation
  • DB migration generation
  • Long-form Spec generation
  • ui-proto screen generation
  • E2E scenario writing/execution

Input

/peach-intake "요청 자연어"
/peach-intake prd=<PRD 경로>
/peach-intake spec=<Spec 경로> [proto=<ui-proto 경로>] [schema=<schema 경로>]
/peach-intake "기존 기능에 승인/반려 상태 추가"
Input Meaning
Natural language request A development request that has not yet been refined
prd PRD source document. A source for checking omissions, not an implementation criterion
spec An already written implementation criterion
proto ui-proto task folder
schema DB schema or migration criterion

If the input is too short or ambiguous, ask questions immediately. However, limit questions to 1–3 and do not proceed to implementation.

Decision criteria

For the detailed decision table, refer to references/decision-matrix.md.

Task scale

Scale Criteria Recommended path
소 Single file, clear bug, no DB/permission/state changes Direct fix or peach-team-3a
중 Single module, 2 or fewer of API/Store/UI, some criteria exist After reinforcing the necessary criteria, peach-team-dev
대 New module, multiple screens, state transitions, permissions, DB changes, PRD-based peach-gen-specStart with

Whether criteria are needed

Criteria Needed signal
Spec Permissions, state transitions, error cases, API expected values, TEST_ID are needed
DB New tables/columns/indexes/state values or a data history structure are needed
ui-proto New complex screens, multi-step forms, multiple modals, tabs, charts, or planner screen review are needed
E2E User flows, screen differences by permission, post-save result verification, or integrated flow validation are needed

Processing flow

  1. Check the input materials.
  2. Determine the task type.
  3. Classify the task scale as small/medium/large.
  4. Determine whether Spec, DB, ui-proto, and E2E are needed.
  5. Separate criteria conflicts or ambiguous items into *_REQUIRED.
  6. Suggest the execution order of follow-up skills.
  7. Report the Intake results.

Result classification

Classification Meaning Handling
READY_FOR_DEV Implementation criteria are sufficient peach-team-devProceed to
SPEC_REQUIRED Implementation criteria are insufficient peach-gen-spec execution
SPEC_REVIEW_REQUIRED A Spec exists, but TEST_ID/permissions/status/error criteria are weak Reinforce Spec
DB_REQUIRED DB structure creation is needed peach-gen-db execution
DB_DECISION_REQUIRED DB judgment is ambiguous Proceed with the DB stage after user decision
PROTO_RECOMMENDED ui-proto increases first-pass completeness peach-team-ui-proto recommended
PROTO_REQUIRED Without screen interpretation verification, there is a high possibility of rework ui-proto first
E2E_REQUIRED User flow verification is needed After implementation, peach-team-e2e
PRD_TO_SPEC_REQUIRED There are requirements in the PRD but not in the Spec Proceed after reinforcing the Spec
DECISION_REQUIRED Judgment of permissions/policies/state transitions is needed User confirmation

Output format

# Intake 결과

## 작업 판정
- 유형: [신규 기능/기존 기능 수정/버그/E2E 검증/문서화]
- 규모: [소/중/대]
- 영향 범위: [backend/frontend/fullstack/e2e/docs]
- 기준 신뢰도: [높음/중간/낮음]

## 기준 필요 여부
| 기준 | 판정 | 근거 |
|------|------|------|
| Spec | 필요/불필요/보강 필요 | ... |
| DB | 필요/불필요/결정 필요 | ... |
| UI Proto | 필수/권장/생략 가능 | ... |
| E2E | 필요/선택/불필요 | ... |

## 권장 실행 경로
1. [후속 스킬 또는 직접 수정]
2. [...]

## 차단 항목
| 분류 | 내용 | 필요한 결정 |
|------|------|-------------|
| DECISION_REQUIRED | ... | ... |

## Intake 판단 근거
- ...

## 사후 피드백 포인트
- 실제 개발 중 이 판정이 맞았는가
- 누락된 기준은 무엇인가
- 다음 intake에서 추가로 확인해야 할 질문은 무엇인가

Follow-up skill mapping

Situation Next skill
Requirements refinement needed peach-gen-spec
DB schema/migration needed peach-gen-db
Mock screens for planning review needed peach-team-ui-proto
Full development needed peach-team-dev
Final flow verification needed peach-team-e2e
Small single feature peach-team-3a
Existing feature analysis needed peach-doc-feature
Standalone DB check needed peach-db-query

Completion criteria

  • Determined the size and type of the work.
  • Clarified whether Spec/DB/ui-proto/E2E are needed, along with the rationale.
  • Before implementation, separate blocking criteria into *_REQUIRED.
  • Suggested the next execution skills and order.
  • Did not directly generate code, DB, proto, or E2E artifacts.