Skip to content

team-workflow.md

Latest commit

 

History

History
81 lines (62 loc) · 2.82 KB

team-workflow.md

File metadata and controls

81 lines (62 loc) · 2.82 KB
Raw

Piko Team Workflow

简体中文

This document contains all team-specific behavior used by Piko.

High-Level Flow

flowchart TD
    A([You]) --> B[Team Lead proposes plan]
    B --> C{Approve plan?}
    C -- Feedback --> B
    C -- Yes --> P[Product defines scope]
    P --> V[Designer prepares UI]
    V --> D[Developer implements]
    D --> E[Code Reviewer evaluates]
    E -- FAIL --> D
    E -- PASS --> F([Preview delivered])
    F --> G{Project done?}
    G -- More feedback --> D
    G -- End --> A

    style A fill:#4a9eff,color:#fff
    style F fill:#2ecc71,color:#fff
Loading

Team Phases

Phase What happens User action
Create Team Lead gathers intent and scope Describe what to build
Design Team Lead proposes implementation plan Approve or request changes
Execute Developer implements and Reviewer validates Monitor or cancel
Complete Team returns preview and summary Give feedback or end project

Team Roles

Role Responsibility
Team Lead Owns product direction, breaks work down, coordinates delegation
Product Manager Defines requirements, scope, and acceptance criteria
UI Designer Defines layout, visual system, and interaction
Developer Writes and updates code, runs builds/tests, integrates fixes
Code Reviewer Checks quality and requirement alignment, issues PASS/FAIL

Control Loops

  • Design loop: Lead iterates on plan until approval
  • Review loop: Reviewer sends fixes back to Developer (bounded retry cycles)
  • Delivery loop: User reviews preview, requests changes, or closes the task

Preview Resolution

When work is marked complete, Piko tries to make output immediately viewable:

Output type Resolution behavior
Static files (html/css/js) Served directly
Build artifacts (dist/, out/) Served as static site
Runnable service (Express/Flask/etc.) Launches service and resolves preview URL

Default Team Presets

Name Team Role Default profile
陈峰 Lead Planning and delegation
王欣 Product Manager Requirements and acceptance criteria
许琳 UI Designer Visual and interaction design
张伟 Developer General-purpose development
李敏 Reviewer Code quality review
林悦 Developer Frontend focus
周宁 Developer Backend focus
赵凯 Developer Rapid prototyping

Notes

  • Team behavior is orchestrated by packages/orchestrator.
  • Prompting, delegation, result finalization, and retry boundaries are handled in the orchestrator runtime.

The default team includes lead, product manager, designer, developer, and reviewer. Members can be added later. Skip product/design steps when irrelevant or already complete; forward their deliverables and paths to downstream workers.