feishu-pm-workflow

---

name: feishu-pm-workflow version: 1.0.0-redskill description: Use when a user wants to initialize, organize, archive, or maintain a product/project workspace in Feishu/Lark with lark-cli: project overview docs, one project management Base, source index, requirement pool, competitor matrix, task plan, risk/decision log, and optional handoff to beautiful-feishu-whiteboard from local files or existing Feishu materials.

Feishu PM Workflow

Build and maintain a structured Feishu/Lark PM workspace from messy project materials.

This RedSkill package keeps the folder structure, but every file is Markdown so it can be uploaded to platforms that only accept .md or .txt.

When To Use

• The user wants to initialize a new PM/product/project workspace in Feishu.
• The user has local files, Feishu docs, meeting notes, chat records, research, PRD drafts, or competitor notes that need systematic archiving.
• The user wants ongoing project updates: ingest new notes, update requirements/tasks/risks, generate a weekly report, or prepare review materials.
• The user asks to connect PM workflow, project management, product discovery, PRD, task planning, or review whiteboards with lark-cli.

Do not use this for a one-off visual board only. If a whiteboard-only skill such as beautiful-feishu-whiteboard is available, use that directly.

RedSkill Package Rules

• Do not depend on executable files. This package intentionally has no .mjs, .sh, .py, .yaml, or test files.
• Use references/lark-cli-commands.md as the replacement for the original helper scripts.
• Run commands directly with lark-cli after showing or explaining the plan.
• Stop if lark-cli is missing or unauthenticated.

Preflight

Before writing to Feishu, run:

node -p 'Number(process.versions.node.split(".")[0])'
lark-cli --help
lark-cli auth status

Requirements:

• Node.js 20 or newer.
• lark-cli installed.
• lark-cli auth status succeeds.

If lark-cli is missing or unauthenticated, tell the user how to install or log in, then stop.

Choose The Mode

Use references/workflows.md to choose one mode:

1. Initialize: create a new project workspace.
2. Archive: classify existing local or Feishu materials and place them into the right project objects.
3. Advance: update an existing workspace from new notes, feedback, PRD changes, or meeting outcomes.

If the mode is unclear, ask one question:

你希望我这次主要做“新项目初始化”，还是“整理已有项目资料”？

Default Workspace

Use references/object-schemas.md for object names and table schemas. The default workspace contains:

• <项目名> - 项目总览 document
• <项目名> - 项目管理 Base app
• tables inside the Base: 资料索引, 需求池, 竞品矩阵, 任务计划, 风险与决策日志
• optional project overview whiteboard generated by beautiful-feishu-whiteboard

Execution

For initialization, follow references/lark-cli-commands.md:

1. Create the project overview document.
2. Create one project management Base.
3. Create the five tables inside the Base.
4. If a real whiteboard is needed, prepare a whiteboard brief in the agent reply and route it to beautiful-feishu-whiteboard when available.
5. Append the Base link and any real whiteboard link back to the project overview.

For archiving, follow references/archive-rules.md. Use lark-cli base +field-list before writing records, then lark-cli base +record-upsert with a top-level field map JSON.

For PRD or project brief output, follow references/prd-template.md.

For visual review material, follow references/whiteboard-briefs.md. Do not create a separate Feishu document that only contains a whiteboard prompt unless the user explicitly asks to persist the brief.

Safety Rules

• Prefer planning or explicit confirmation before write operations.
• Create or reuse existing Feishu objects; never create duplicates without telling the user.
• Do not delete the default empty Base table unless the user explicitly asks.
• Do not represent a whiteboard brief document as a finished whiteboard. A brief is only an input to whiteboard generation.
• Keep source evidence traceable.
• Mark assumptions, priority decisions, scope tradeoffs, and launch timing as needs confirmation.
• Do not put raw private source material into a public-facing whiteboard.
• If writing fails, report which objects were created, which failed, and what can be safely retried.

Delivery

Return:

1. Project overview link.
2. Project management Base link.
3. Real whiteboard link if generated, or the whiteboard brief in the chat reply.
4. Created or updated table list.
5. Summary of created or updated objects.
6. Items requiring user confirmation.
7. Suggested next commands.

Files

• references/workflows.md: mode selection and step-by-step flows.
• references/object-schemas.md: default Feishu object names and table schemas.
• references/lark-cli-commands.md: command-by-command creation workflow.
• references/archive-rules.md: material classification and extraction rules.
• references/prd-template.md: project brief and PRD templates.
• references/whiteboard-briefs.md: rules for producing a brief and handing it to beautiful-feishu-whiteboard.