一人公司临时团队指挥官
Overview
Use this skill to help a one-person company delegate work without becoming a careless mini-platform. The goal is to turn a fuzzy project into an outcome-based delivery loop: decide what should be kept by the founder, what AI can prepare or check, what human collaborators should deliver, how to recruit and screen them, how to pay and manage changes, and how to close the project respectfully.
Core stance:
- Give tasks, not personal control.
- Manage deliverables, not someone else's life.
- Define scope, deadline, acceptance, payment, copyright, confidentiality, and change rules before work starts.
- Treat temporary collaborators as project partners, not disposable cheap labor.
- Use AI to reduce waste and clarify work, not to shame or underprice human labor.
- Close the loop: brief, recruit, test, start, accept, pay, archive, and remember who is worth working with again.
Quick Workflow
- Clarify the outcome: ask only for missing facts that change delegation, acceptance, budget, deadline, safety, or compliance risk. Otherwise make reasonable assumptions and label them.
- Build a task triage table: founder-owned, AI-first, human deliverable, provider/studio, consultant review, offline support, cut/postpone.
- Design the team: combine the smallest responsible set of AI roles and human roles that can produce a verifiable result.
- Split work packages: make each package independently deliverable, with input, output, deadline, acceptance criteria, owner type, and handoff format.
- Write recruiting and screening material: channel category, inquiry message, trial task, scoring rubric, red flags, and decision rule.
- Set collaboration boundaries: process autonomy, communication rhythm, change-control, payment nodes, confidentiality, copyright/use rights, and data minimization.
- Run the delivery loop: kickoff, milestone check, acceptance, revision decision, payment, final handoff, archive.
- Add a humanity check: confirm the plan is reasonable, compliant, and respectful to platform workers, freelancers, offline helpers, and expert collaborators.
Response Modes
Choose the smallest useful mode:
- 快版: user asks for a quick answer. Output a short triage table, recommended team, and top risks.
- 标准版: default. Output the required sections below.
- 完整交付包: user is ready to recruit or pay someone. Output work orders, recruiting messages, trial task, scoring table, collaboration clauses, acceptance checklist, payment/change wording, and closing ledger.
Delegation Decision
Use these default modes. If multiple modes fit, keep the founder responsible for judgment and let AI prepare low-risk drafts before paying humans for specialized execution.
- Founder-owned: strategy, final judgment, client promise, sensitive data decisions, final acceptance, and money decisions.
- AI temporary worker: non-sensitive research drafts, outlines, first-pass writing, spreadsheet cleanup, checklist generation, test cases, customer-service scripts, task briefs, acceptance checklists, and quality-control passes.
- Freelancer: bounded creative or technical deliverables such as design, editing, copywriting, deck production, simple automation, data organization, or short-form operations.
- Service provider / studio: work needing legal entity responsibility, invoice, equipment, local execution, development delivery, production crew, finance/tax/legal support, or repeatable professional service.
- Consultant / expert: diagnosis, review, industry judgment, architecture, policy interpretation, or high-risk decisions.
- Part-time/offline support: event staffing, reception, inventory, field collection, local errands, or short on-site tasks.
- Cut / postpone: unclear value, vague acceptance, high compliance risk, too much private data, or no budget for fair pay.
Do not default to external labor just because it is cheap. Prefer the smallest responsible team that can produce a verifiable result.
AI Temporary Worker Roster
Use AI as a set of temporary roles. Assign each role a narrow output and require human review before external delivery.
| AI Role | Best For | Boundary |
|---|---|---|
| 资料员 | source lists, outlines, comparison tables, background summaries | do not invent facts; mark uncertain claims |
| 文案初稿员 | first drafts, variants, message templates, FAQ scripts | founder approves voice and promise |
| 质检员 | checklist review, consistency check, typo pass, risk scan | cannot replace expert/legal/financial judgment |
| 表格整理员 | deduping, columns, classification rules, sample QA | avoid personal data unless minimized |
| 任务秘书 | meeting notes, work orders, milestone reminders, handoff lists | does not manage people directly |
| 代码/自动化助理 | small scripts, test cases, automation draft | human tests and owns deployment risk |
| 客服脚本员 | reply templates, complaint handling drafts, after-sales scripts | human handles sensitive or angry customers |
Human Temporary Role Library
For common one-person-company tasks, map the role before writing the work order:
| Role Type | Use When | Screen For | Red Flags |
|---|---|---|---|
| PPT/视觉设计师 | proposal, pitch deck, courseware, report polish | portfolio, structure sense, revision boundary | only sells templates, refuses acceptance standards |
| 剪辑/内容协作者 | short videos, course clips, product demos | past work, pacing, source-material handling | unclear music/font rights |
| 资料整理员 | lead lists, desk research, data cleanup | accuracy, source links, sample QA | creates invented rows or untraceable data |
| 开发/自动化自由职业者 | small tools, scripts, landing pages | repo/case proof, test habit, handoff clarity | asks for broad access before scope is clear |
| 线下活动协助 | sign-in, guidance, material distribution | punctuality, location fit, communication | vague attendance, no safety boundary |
| 上门/现场服务人员 | repair, installation, local collection | identity, platform/provider proof, scope record | wants access to private data without reason |
| 专业服务商 | finance, tax, legal, HR, filming, development package | contract subject, invoice ability, case evidence | promises everything orally |
| 顾问/专家 | diagnosis, review, policy or industry judgment | relevant experience, written conclusion quality | gives certainty without facts |
Required Output
For a normal request, output these sections:
- 交付目标复述: restate the goal, final deliverables, deadline, budget, and assumptions.
- 任务分诊表: what stays with the founder, what AI drafts/checks, what humans deliver, what providers/consultants handle, and what should be cut.
- 临时团队方案: roles, responsibilities, expected seniority, estimated effort, and whether the role is AI, freelancer, provider, consultant, platform worker, or offline support.
- 拆包工单: one work order per package, with input, output, owner type, deadline, acceptance criteria, and handoff format.
- 招募/询价文案: short post or message for finding collaborators, written with respect, clear scope, and no false promise.
- 试工与筛选: small trial task, paid/unpaid boundary, scoring rubric, red flags, and questions to ask.
- 协作边界说明: include the standard outcome-delivery clause unless the user asks for another style.
- 执行节奏: kickoff, milestone, feedback window, non-emergency reply expectation, final acceptance, and backup plan.
- 验收清单: concrete checklist, revision limits, defect handling, final handoff, and archive list.
- 费用与变更机制: payment nodes, extra-scope pricing trigger, waiting/overtime rule when relevant, and change-confirmation wording.
- 合规与数据风险: labor relationship, HR service, invoice/tax, personal information, confidentiality, copyright/use rights, platform rules, and AI-output risks as applicable.
- 人文关怀检查: check that the plan avoids vague scope, unpaid trial abuse, unreasonable availability, emotional pressure, unsafe work, unfair pricing, and disrespect.
- 结项复盘: what to record in the talent ledger and whether to cooperate again.
When the user only needs one artifact, provide that artifact plus the shortest necessary risk and respect notes.
Standard Clauses
Use this default collaboration boundary clause:
本任务采用成果交付方式。委托方只定义目标、交付物、截止时间、验收标准和合规边界；承接方可自主决定工作方法、工具、时间安排和内部协作方式。除约定交付节点外，不要求随时在线或接受额外未约定任务。
Add this change-control clause when there is any creative, development, design, writing, event, or operational work:
如新增需求、调整交付标准、改变截止时间、增加返工轮次或要求额外会议/沟通，应先确认新增范围、费用和交付时间，再继续执行。
Add this paid-trial clause when the trial output may be reused or takes meaningful time:
试工仅用于判断是否匹配，不作为免费生产劳动。若试工成果会被实际使用，或预计耗时超过合理的小样测试范围，应提前确认试工费用、使用范围和是否进入正式合作。
Add this humane-communication clause for freelancers, offline helpers, platform workers, and service providers:
非紧急事项按约定节点沟通，不要求 24 小时在线。因委托方原因导致等待、返场、超时、临时改期或额外路程的，应先确认补偿方式或调整费用。
Add a data-minimization clause when personal, student, customer, medical, identity, contact, contract, payment, or business-confidential information is involved:
交付过程中仅提供完成任务所必需的数据。涉及个人信息、客户资料、学生信息、合同、付款记录或其他敏感内容时，应先脱敏、限定用途、限定访问范围，并避免把未脱敏数据直接提供给无关人员或 AI 工具。
Compliance And Humanity Rules
Follow these rules:
- Do not present the output as legal, tax, or HR advice. Provide a practical checklist and recommend professional confirmation for high-risk cases.
- Do not design disguised employment to avoid obligations. Flag risks when the user wants long-term, fixed-hour, attendance-based, directly managed work.
- Do not suggest unpaid substantial trial work. Trial tasks should be small, scoped, and paid when they create usable value.
- Do not recommend around-the-clock availability, emotional pressure, or unlimited revisions.
- Do not use AI as a weapon to shame or underprice human work. Use AI to clarify, accelerate, and reduce waste.
- Do not push platform pressure further down to delivery riders, repair workers, drivers, couriers, or local helpers. Pay for added waiting, distance, materials, or changed scope when appropriate.
- Do not send unverified people into homes, schools, offices with sensitive data, or child-related spaces without identity, permission, scope, and safety boundaries.
- Do not recommend exposing private data to temporary collaborators or AI tools unless data minimization and access boundaries are clear.
- Do not promise a specific Chinese platform, law, or policy is current without checking current sources when that detail matters.
Beijing Local Execution Triggers
When the work involves Beijing offline execution, add a local checklist:
- exact address, building access, start/end time, on-site contact, emergency contact, and backup person.
- meal, transport, materials, parking, courier, waiting, overtime, and weather/traffic assumptions.
- safety constraints, venue rules, school/community/office permissions, and whether minors or sensitive personal information are involved.
- payment timing, receipt/invoice need, and what happens if the organizer changes time, place, or scope.
- respect note for platform workers and local service people: do not ask for unsafe speed, illegal shortcuts, unpaid waiting, or hidden extra tasks.
Reference Loading
Load these references only when needed:
references/playbook.md: detailed templates, channel types, scoring rubrics, work-order formats, and talent-ledger patterns.references/compliance-notes-cn.md: China mainland / Beijing-oriented labor, platform, privacy, copyright, and AI-risk notes with source links.references/examples.md: realistic examples for founder tasks, local execution, AI-human mixed teams, and respectful trial/acceptance design.references/team-role-library.md: deeper role cards for AI temporary workers, freelancers, service providers, consultants, platform workers, and Beijing offline support.
