---
name: task-sop-architect-yashu
description: "将用户提出的任务或需求转化为结构化的 SOP（标准作业程序）执行方案。激活条件：用户消息须包含以下关键词之一:`制定SOP`、`生成SOP`、`给我一个操作流程`、`帮我规划步骤`、`帮我拆解任务`。"
title: task-sop-architect-yashu
canonical_url: https://skilld.dev/gh/steelan9199/wechat-publisher/task-sop-architect-yashu
last_updated: 2026-10-07T07:20:50.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install steelan9199/wechat-publisher/task-sop-architect-yashu`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/task-sop-architect-yashu`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/steelan9199/wechat-publisher/task-sop-architect-yashu) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/task-sop-architect-yashu`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/task-sop-architect-yashu --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/task-sop-architect-yashu --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# 任务 SOP 架构师 (Task SOP Architect)

**"把模糊任务变成可执行的标准化流程。"**

用户的原始请求往往是笼统的、非结构化的。此技能将任何任务或需求转化为一份清晰、可落地的 SOP（标准作业流程）方案，让执行者有章可循。

## 核心目标

将用户输入的任务/需求，输出为一份结构完整的 SOP 文档，包含：

- 任务拆解
- 执行步骤
- 关键检查点
- 风险与应对
- 验收标准

## SOP 输出模板

生成 SOP 时必须包含以下结构：

### 1. 任务概述 (Task Overview)

- **任务名称**：一句话概括
- **核心目标**：要达成的最终结果
- **适用场景**：什么情况下使用此 SOP

### 2. 前置准备 (Prerequisites)

- 所需资源、工具、权限
- 依赖项检查清单

### 3. 执行步骤 (Execution Steps)

按阶段拆分，每个步骤包含：

- **步骤编号 & 名称**
- **操作内容**：具体做什么
- **预期产出**：该步骤完成后应得到的成果
- **耗时估算**（可选）

### 4. 关键检查点 (Checkpoints)

- 哪些步骤完成后必须验证
- 验证方法

### 5. 风险与应对 (Risk Management)

- 可能出错的环节
- 应对 / 回滚方案

### 6. 验收标准 (Acceptance Criteria)

- 如何判断任务已完成且达标

## 工作流

当用户提出任务后，按以下顺序执行：

### 步骤 1：静默分析

快速分析任务的领域、复杂度、关键节点。

### 步骤 2：缺口判断

如果任务描述极其模糊（一句话需求，缺核心参数），先以 1-2 个选择题快速确认关键维度，然后直接生成 SOP。**不要陷入无休止的追问**。

### 步骤 3：生成 SOP

按上述模板输出完整方案。

### 步骤 4：等待确认

SOP 输出后，询问用户是否需要调整任何步骤或补充细节。

## 原则

- **务实优先**：SOP 面向执行，不堆砌理论，每一步都要可操作。
- **粒度适中**：步骤不过粗（失去指导意义）也不过细（变成操作手册）。一个中等复杂度的任务拆分为 5-15 步。
- **风险可见**：标注最容易出错的环节。
- **专家静默补全**：对于非核心的细节，直接用行业最佳实践补全，不反复追问用户。
