Back to Details

postplus-workspace

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

PostPlus Workspace

PostPlus工作区

Turn one resolved project folder into the durable context and control surface for repeated PostPlus work. Use 
postplus-shared
first for shared public rules, source-of-truth guidance, work-folder handling, and local dependency handling. This skill owns workspace orchestration. Specialist PostPlus skills own domain judgment. The current PostPlus CLI and server own schemas, validation, cost, permissions, and provider execution.
将一个已确定的项目文件夹转变为可重复进行PostPlus工作的持久化上下文与控制界面。请先使用
postplus-shared
来处理共享公共规则、权威指导、工作文件夹管理及本地依赖项。本skill负责工作区编排，专业PostPlus技能负责领域判断，当前PostPlus CLI与服务器负责模式定义、验证、成本、权限及供应商执行。

Core Contract

核心约定

  1. Read the workspace before acting.
  2. Keep confirmed facts, approved claims, research findings, hypotheses, defaults, unknowns, and forbidden content distinct.
  3. Never invent product facts, prices, offers, identities, references, permissions, approvals, or results.
  4. Ask only when missing or conflicting information changes truth, strategy, identity, execution, compliance, spend, or publishing.
  5. Make reversible low-risk production choices without asking.
  6. Discover current PostPlus capabilities by catalog and CLI schema instead of maintaining a hard-coded skill inventory.
  7. Require explicit approval before changing approved truth, approving a test plan, spending credits, launching, publishing, or changing live ads.
  8. Return durable results and decisions to the workspace.
  1. 操作前先读取工作区内容。
  2. 明确区分已确认事实、获批声明、调研结果、假设、默认值、未知项及禁用内容。
  3. 不得虚构产品事实、价格、优惠、身份、参考资料、权限、审批或结果。
  4. 仅当缺失或冲突信息会影响事实、策略、身份、执行、合规、支出或发布时才发起询问。
  5. 无需询问即可做出可逆的低风险生产决策。
  6. 通过目录和CLI模式了解当前PostPlus能力，而非维护硬编码的skill清单。
  7. 在修改已获批事实、批准测试计划、消耗额度、发布、上线或更改在线广告前，需获得明确审批。
  8. 将持久化结果与决策返回至工作区。

Route

路由规则

RequestRoute
Start a PostPlus project folderInitialize workspace
Start a campaign or test cycleInitialize campaign
Continue an existing projectResume workspace
Diagnose missing contextCheck the requested stage
Research, strategy, testing, or productionRead stage context, then route to the current specialist skill
Quote, launch, publish, or change spendValidate with the current CLI, then obtain explicit approval
Analyze performanceRecord observations, conclusions, scope, and next hypothesis
请求路由
启动PostPlus项目文件夹初始化工作区
启动营销活动或测试周期初始化活动
继续现有项目恢复工作区
诊断缺失上下文检查指定阶段
调研、策略制定、测试或生产读取阶段上下文，然后路由至当前专业skill
报价、发布、上线或更改支出通过当前CLI验证，然后获取明确审批
分析性能记录观察结果、结论、范围及下一个假设

Initialize Workspace

初始化工作区

  1. Resolve the exact target folder and inspect existing files.
  2. Run 
    postplus doctor --skill postplus-workspace --json
    . Follow 
    postplus-shared
    if the Python 3 dependency is missing.
  3. Resolve this installed skill directory and run:
text
<python-3-command> <skill-directory>/scripts/workspace.py init \
  --target <folder> --project "<project name>" \
  [--brand "<brand>"] [--product "<product>"] \
  [--market "<market>"] [--platform "<platform>"] \
  --output <folder>/.postplus/workspace-init.json
Pass only user-supplied or reliably sourced values. The entrypoint creates missing files only and rejects filesystem roots, the user home directory, and installed skill directories.
Read existing source materials, fill only confirmed information, preserve 
UNKNOWN
, then run the onboarding check.
  1. 确定准确的目标文件夹并检查现有文件。
  2. 运行
    postplus doctor --skill postplus-workspace --json
    。若缺失Python 3依赖项，请遵循
    postplus-shared
    的指引。
  3. 找到已安装的本skill目录并运行：
text
<python-3-command> <skill-directory>/scripts/workspace.py init \
  --target <folder> --project "<project name>" \
  [--brand "<brand>"] [--product "<product>"] \
  [--market "<market>"] [--platform "<platform>"] \
  --output <folder>/.postplus/workspace-init.json
仅传入用户提供或来源可靠的值。入口仅创建缺失文件，拒绝文件系统根目录、用户主目录及已安装的skill目录。
读取现有源材料，仅填充已确认信息，保留
UNKNOWN
标记，然后运行入职检查。

Initialize Campaign

初始化活动

Run:
text
<python-3-command> <skill-directory>/scripts/workspace.py new-campaign \
  --target <workspace> --name "<campaign name>" [--slug <campaign-slug>] \
  --output <workspace>/.postplus/campaign-init.json
Fill the objective, market, platform, offer, CTA, KPI, constraints, and approval state. Set 
current_campaign
in 
project.yaml
only after confirming the intended campaign.
运行：
text
<python-3-command> <skill-directory>/scripts/workspace.py new-campaign \
  --target <workspace> --name "<campaign name>" [--slug <campaign-slug>] \
  --output <workspace>/.postplus/campaign-init.json
填写目标、市场、平台、优惠、CTA、KPI、约束条件及审批状态。仅在确认目标活动后，才在
project.yaml
中设置
current_campaign
。

Resume And Execute

恢复与执行

  1. Find the nearest 
    project.yaml
    at or above the working directory.
  2. Read the nearest applicable 
    AGENTS.md
    , then 
    project.yaml
    .
  3. Read only the stage context listed in context-schema.md.
  4. Run the workspace stage check before high-impact execution.
  5. Read the selected specialist skill completely.
  6. Read current CLI help or schema immediately before CLI execution.
  7. Continue from recorded state instead of recreating prior work.
If no workspace exists, offer initialization. Do not scatter project files into an unrelated folder.
  1. 在工作目录或其上级目录中查找最近的
    project.yaml
    文件。
  2. 读取最近适用的
    AGENTS.md
    ，然后读取
    project.yaml
    。
  3. 仅读取context-schema.md中列出的阶段上下文。
  4. 在高影响执行前运行工作区阶段检查。
  5. 完整读取所选专业skill的内容。
  6. 在执行CLI前立即读取当前CLI帮助或模式。
  7. 从已记录的状态继续，而非重复之前的工作。
若工作区不存在，提供初始化选项。不得将项目文件分散到无关文件夹中。

Stage Rules

阶段规则

Follow stage-gates.md for onboarding, research, strategy, test, production, launch, and learning requirements. The bundled checker validates workspace files only; current quotes, provider validation, permissions, accounts, and live state remain authoritative at the CLI or server boundary.
Read uncertainty-policy.md when information is missing, conflicting, or a repair could change meaning.
遵循stage-gates.md中关于入职、调研、策略制定、测试、生产、发布和学习的要求。内置检查器仅验证工作区文件；当前报价、供应商验证、权限、账户及在线状态以CLI或服务器边界的信息为准。
当信息缺失、冲突或修改可能改变含义时，请阅读uncertainty-policy.md。

Check Workspace

检查工作区

text
<python-3-command> <skill-directory>/scripts/workspace.py check \
  --target <workspace> \
  --stage <onboarding|research|strategy|test|production|launch|learn> \
  [--campaign <campaign-slug>] \
  --output <workspace>/.postplus/stage-check.json
Treat 
BLOCKED
as a stop for the affected stage. A local 
READY
result does not replace current CLI validation, quote confirmation, or launch approval.
text
<python-3-command> <skill-directory>/scripts/workspace.py check \
  --target <workspace> \
  --stage <onboarding|research|strategy|test|production|launch|learn> \
  [--campaign <campaign-slug>] \
  --output <workspace>/.postplus/stage-check.json
将
BLOCKED
视为对应阶段的停止信号。本地
READY
结果不能替代当前CLI验证、报价确认或发布审批。

Status

状态报告

End substantive tasks with:
text
STAGE: <stage>
STATUS: READY | BLOCKED | NEEDS_APPROVAL | COMPLETED
INPUTS READ: <sources>
BLOCKERS: <none or exact blockers>
OUTPUTS: <created or updated artifacts>
NEXT: <one next action>
完成实质性任务后输出：
text
STAGE: <stage>
STATUS: READY | BLOCKED | NEEDS_APPROVAL | COMPLETED
INPUTS READ: <sources>
BLOCKERS: <none or exact blockers>
OUTPUTS: <created or updated artifacts>
NEXT: <one next action>

Resources

资源

  • context-schema.md: ownership and loading rules
  • stage-gates.md: stage and approval gates
  • uncertainty-policy.md: ask, assume, and repair boundaries
  • assets/project-template/
    : workspace and campaign templates
  • scripts/workspace.py
    : non-destructive initialization and local stage checks
  • context-schema.md: 所有权与加载规则
  • stage-gates.md: 阶段与审批关卡
  • uncertainty-policy.md: 询问、假设与修正边界
  • assets/project-template/
    : 工作区与活动模板
  • scripts/workspace.py
    : 非破坏性初始化与本地阶段检查