SoftwareCopyright-Skill Skill
What it does
中国软件著作权申请材料 生成器 Skills,本 Skills 通过阅读本地项目,自动生成全套 .docx 软著申请材料,全开源,无须再付费购买任何软著申请服务
- Connects Instruction files the AI reads; connects to nothing
- Account or key No key needed
- Category Other
For makers: add a badge to your README
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/skills/fokkyp-softwarecopyright-skill)Similar Skills
Same kind of work, ordered like the Skills list
| This one SoftwareCopyright-Skill | llmfit | claude-video | VideoCaptioner | patent-disclosure-skill | |
|---|---|---|---|---|---|
| Maker | Fokkyp | AlexsJones | bradautomates | WEIFENG2333 | handsomestWei |
| Skills | 1 | 1 | 1 | 1 | 1 |
| GitHub stars | 6,366 | 39,004 | 20,889 | 16,539 | 13,468 |
| Last code change | Oct 23, 2026 | Nov 12, 2026 | Sep 25, 2026 | Sep 12, 2026 | Nov 15, 2026 |
| License | AGPL-3.0 | MIT | MIT | GPL-3.0 | MIT |
1 skills (instruction sets) by Fokkyp that an AI reads and follows · not an MCP server
How a Skill differs from MCP
MCP = the hands
Connects the AI to an outside service or data, such as reading Notion or creating an invoice. A program or server has to be running.
Skill = the manual
A text file that teaches the AI how to do a task. It connects to nothing.
Some overlap: a few Skills run scripts that call tools, and a few MCP servers only send knowledge. Start from the task you want done.
Works with
Not stated by the maker · SKILL.md skills work in apps that support Agent Skills, such as Claude Code, Codex and Cursor
Install
Is it safe?
- Who made it
GitHub account Fokkyp (person), 13 years old
- Use and upkeep
★ 6,366 stars · code last changed Oct 23, 2026
- Any scripts?
17 scripts that can run on a computer: scripts/analyze_project.py, scripts/build_docx_from_md.py, scripts/capture_screenshots.py, scripts/check_environment.py and 13 more
- Uses the internet?
Could not check every script (some are too large); read them first
- Changes machine-wide settings?
No hooks or writes to machine settings found
Checked automatically from the repo files at commit 1159f6d (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
First: which AI do you use?
Pick your app and this page shows only how to install it there
Option 1Upload to claude.ai (web and app)
Download from GitHub
This skill uses the AGPL-3.0 license, which is not on the list we redistribute, so we do not hand out a ZIP from our site. Download it from GitHub and arrange the folder yourself, or use "Let the AI install it" above, which is easier
Download from GitHub (whole repo) ↗
Unzip it, then zip only the software-copyright-materials folder again. The ZIP must have a software-copyright-materials folder with SKILL.md at the top level, no loose files
Open Skills on claude.ai and upload
+Create skillUpload a skillpick software-copyright-materials.zip
No Upload button? Turn on file creation first
SettingsCapabilitiesCode execution and file creation
Turn on Code execution and file creation first (newer menus: Create and edit files) · personal plans: Settings → Capabilities · Team/Enterprise: an admin turns it on under Organization settings → Plugins & skills · every plan, including Free
Upload once; it works in claude.ai and Claude Desktop, and in recent Claude Code signed in with a Claude account (not with an API key)
Cowork and cloud sessions use the skills turned on in your claude.ai account, not ~/.claude/skills on your computer (Claude Desktop scheduled tasks run locally and still load it)
Checked against official docs Nov 12, 2026 · Source: support.claude.com, support.claude.com, code.claude.com
Option 1Let Claude Code install it
Copy this sentence and paste it into a Claude Code chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Restart Claude Code, then type /software-copyright-materials or ask for a matching task and Claude picks it up
Checked against official docs Nov 12, 2026 · Source: code.claude.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.claude/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/fokkyp/softwarecopyright-skill.git /tmp/popnx-skill-fokkyp-softwarecopyright-skill-1159f6d && mkdir -p ~/.claude/skills && cp -R '/tmp/popnx-skill-fokkyp-softwarecopyright-skill-1159f6d/software-copyright-materials' ~/.claude/skills/software-copyright-materialsRestart Claude Code, then type /software-copyright-materials or ask for a matching task and Claude picks it up
ChatGPT desktop app
The ChatGPT desktop app has Codex built in, and Codex reads skills from ~/.agents/skills
Option 1Let ChatGPT install it
Open Codex in the ChatGPT desktop app and paste this sentence into the chat
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Option 2Put the folder there yourself
Put the software-copyright-materials folder at ~/.agents/skills/software-copyright-materials
~ is your home folder ($HOME)
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.agents/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/fokkyp/softwarecopyright-skill.git /tmp/popnx-skill-fokkyp-softwarecopyright-skill-1159f6d && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-fokkyp-softwarecopyright-skill-1159f6d/software-copyright-materials' ~/.agents/skills/software-copyright-materials
After installing
- ChatGPT desktop app: open Skills in the sidebar to see that the skill is there
- To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
- Codex picks up newly installed skills by itself; if one does not show up, restart Codex
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
ChatGPT on the web and mobile
Skills you install yourself do not work here; only skills that come with a plugin from the directory
To use this skill with ChatGPT, use the ChatGPT desktop app as above
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
Option 1Let Codex install it
Copy this sentence and paste it into a Codex chat · Works in Codex inside the ChatGPT desktop app, Codex CLI and the IDE extension
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex picks up newly installed skills by itself; if one does not show up, restart Codex · To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.agents/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/fokkyp/softwarecopyright-skill.git /tmp/popnx-skill-fokkyp-softwarecopyright-skill-1159f6d && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-fokkyp-softwarecopyright-skill-1159f6d/software-copyright-materials' ~/.agents/skills/software-copyright-materialsRestart Codex, then ask for a matching task; Codex lists the skill
Option 1Let Cursor install it
Copy this sentence and paste it into a Cursor chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
In Cursor’s Agent chat, type / and pick software-copyright-materials
Checked against official docs Nov 12, 2026 · Source: cursor.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.cursor/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/fokkyp/softwarecopyright-skill.git /tmp/popnx-skill-fokkyp-softwarecopyright-skill-1159f6d && mkdir -p ~/.cursor/skills && cp -R '/tmp/popnx-skill-fokkyp-softwarecopyright-skill-1159f6d/software-copyright-materials' ~/.cursor/skills/software-copyright-materialsIn Cursor’s Agent chat, type / and pick software-copyright-materials
Option 1Let the AI install it
For other apps that read skills. The sentence gives the paths for Claude Code, Codex and Cursor so the AI picks the one for your app · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs Nov 12, 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com
For Terminal users
Other apps that support Agent Skills (such as Gemini CLI or GitHub Copilot) use different folders. Check that app’s guide, then copy the folder with the SKILL.md there.
Skill folders checked against the official Claude Code, Codex and Cursor guides on Nov 11, 2026
✓ Commands checked Nov 16, 2026
View the original SKILL.md
The text below comes from the maker’s repo, not from PopNx MCP
Showing the first 8,000 characters · Open the full file on GitHub
---
name: software-copyright-materials
description: >
Generate guided Chinese software copyright application materials from a real project.
Use this skill when the user asks for 软件著作权, 软著申请资料, 软著代码材料,
操作手册, 申请表信息, or wants Word/TXT materials for software copyright registration.
The workflow analyzes the imported project, extracts real source code, creates Markdown
drafts for user confirmation, then uses a pinned OfficeCLI backend to produce final
Word documents and TXT.
metadata:
short-description: 生成软著申请资料 Word/TXT
author: Fokkyp
version: "2.6"
repository: https://github.com/Fokkyp/SoftwareCopyright-Skill
---
# 软著申请资料生成
这个 skill 生成可审阅、可追溯的软著申请资料。核心原则:
- 固定输出目录:当前工作目录下的 `软件著作权申请资料/`。不要默认写到 `/tmp`、`/private/tmp` 或其他临时目录。
- 只有测试 skill 自身时才允许显式指定临时目录;面向用户生成材料时必须写入当前目录。
- 先生成 Markdown 草稿,用户确认后再生成正式 Word/TXT。
- 正式 Word/TXT 只能写入 `软件著作权申请资料/正式资料/`,不要散落在输出目录根部。
- 正式 Word/TXT 的文字一律使用默认黑色字体,不生成蓝色超链接、主题色标题或其他彩色文字;Markdown 链接写入 Word 时必须转成普通文本。
- 正式资料中的软件名称必须与 `草稿/申请表信息.md` 的“软件全称”字段一致;正式生成时以已确认的申请表软件全称为准。
- 正式代码 Word 页眉中的版本号必须与 `草稿/申请表信息.md` 的“版本号”字段一致;正式生成时以已确认的申请表版本号为准。
- 代码材料必须来自真实项目源码,禁止 AI 编造代码。
- 写申请表和操作手册前,必须先形成模型研判后的 `草稿/业务理解.md/json`,理解软件业务、行业、目标用户、核心价值和操作流程。
- 脚本只能收集项目证据、校验字段和生成文件;行业判断、功能抽取、代码抽取选择、操作手册结构必须由模型阅读项目后决定,不得依赖脚本关键字表或固定范本。
- 优先抽取前端代码:入口、路由、页面、核心组件、接口封装、状态管理、工具函数。
- 生成代码材料前,必须先生成代码文件候选清单;模型理解项目后填写抽取文件和选择理由,再让用户确认或修改。
- 代码优先抽取模型和用户确认的、最能体现软件真实功能和运行逻辑的源码;不足 60 页时,从其他相关源码文件补充到 60 页;候选源码仍不足 60 页时,才生成全部代码文档。
- 源码发现不得依赖编程语言扩展名白名单。脚本默认扫描可读文本文件,并排除明确的文档、配置、媒体、压缩包、二进制、生成物和超大文件;未知扩展名源码同样进入候选清单,再由模型和用户确认是否抽取。
- 业务证据收集必须发现项目中的文本设计资料以及 DOCX、PDF、ODT、DOC、WPS 等文档;能自动提取正文时写入证据,无法提取时也必须登记路径并提示模型进一步阅读,不能因格式不在文本扩展名列表中而静默遗漏。
- 操作手册成稿应像真实软件随附的操作说明,而不是研发说明、功能清单或 AI 生成的汇总文。
- 操作手册草稿必须按传统软著操作手册骨架组织:相关文档、说明、功能特点、系统要求、按真实页面/流程逐章操作、常见问题解答、术语表。一级章节标题使用中文大写序号,例如 `一、相关文档`,不得使用 `(1)、相关文档`。相关文档必须用表格指向总体设计、详细设计、测试案例等配套文档。正文尽量使用连续段落,不使用项目符号列表或 `1. 2. 3.` 编号列表。
- 每个核心页面都要用普通用户视角说明页面用途、进入位置、用户可见内容、用户动作、输入限制或异常提示、结果反馈和截图预留。不得把章节写成“进入方式:/页面内容:/操作步骤:/操作规则:/操作结果与反馈:”这种字段模板;这些信息要自然合并到段落里。避免代码、框架、接口、状态管理、异步任务等技术化表达;撰写过程中由 agent 自行循环检查、扩写和修正,完整草稿完成后只向用户发起一次整体确认。
- 操作手册必须去除明显“AI 味”:避免空泛赞美、营销口号、万能句式、每章同一结构、头中尾固定结构、过度对称的排比、没有项目细节的正确废话、频繁使用“旨在、赋能、一站式、智能化、高效便捷、显著提升、强大能力、丰富功能”等套话。每段都应能回答“这个项目里这个功能具体做什么、用户看见什么、操作后有什么结果”。
- 操作手册生成必须同步输出 `草稿/操作手册自检记录.md` 和 `草稿/操作手册自检记录.json`,记录初稿、按项目流程扩写、去制式表达等自检轮次;如果前 3 轮仍发现问题,必须继续补写修正,直到问题清零或记录无法自动修复的原因后再停止。
- 截图方式只允许用户选择:Playwright CLI 自动截图或用户自行截图。用户选择自动截图后,先检查固定验证版本的 `playwright-cli` 是否可用;如果用户说现在不截图、先跳过截图或截图失败,操作手册仍必须保留清晰可见的截图预留位置,正式 Word 中也要能看到。
- 申请表信息中的硬件/系统环境必须让用户确认或填写,不能硬编码。
- Word 生成统一使用 OfficeCLI 后端;Python 只负责业务分析、代码抽取、门禁和命令编排,不直接解包、重打包或写入 DOCX 包。OfficeCLI 完成正文写入后,必须通过 `/theme` + `raw-set` 把主题字体统一为宋体(SimSun)和 Times New Roman,并重新读取主题确认 Calibri、Calibri Light、等线等默认主题字体已消失。
- OfficeCLI 固定验证版本为 `1.0.151`,运行时必须设置 `OFFICECLI_SKIP_UPDATE=1`,不得静默升级、静默安装或回退到 python-docx/Pandoc/.NET 工具包。
- OfficeCLI 的安装、批处理、分页与校验细节见 `references/officecli_backend.md`。
## 路径与按需参考
开始执行前,从当前已加载的 `SKILL.md` 位置取得本 skill 的绝对目录,记为 `<SKILL_DIR>`;找到可用的 Python 3.10+ 解释器,记为 `<PYTHON>`。下面命令中的尖括号是必须替换的占位符,不要依赖 `${CLAUDE_SKILL_DIR}` 等某个 agent 专属环境变量,也不要把占位符原样交给 shell。
按当前阶段读取对应参考资料,不要一次性把所有内容都塞入上下文:
- 填申请表前读 [application_fields.md](references/application_fields.md)。
- 研判业务前读 [business_understanding_rules.md](references/business_understanding_rules.md)。
- 选择和抽取代码前读 [code_selection_rules.md](references/code_selection_rules.md) 与 [copyright_material_rules.md](references/copyright_material_rules.md)。
- 写操作手册前读 [manual_structure.md](references/manual_structure.md)。
- 用户选择自动截图后读 [playwright_cli_screenshots.md](references/playwright_cli_screenshots.md)。
- 正式生成和校验 DOCX 前读 [officecli_backend.md](references/officecli_backend.md)。
## 强制人工门禁
凡是涉及用户选择、确认或补充信息的阶段,必须先停止当前执行,不得继续调用下一步脚本。即使处于自动审核、自动继续或无人值守模式,也必须把 `STOP_FOR_USER` 和 `NEXT_ACTION` 原样告知用户,并等待用户输入后再继续。
禁止使用“用户未选择则默认继续”的逻辑。用户回复确认后,先用确认脚本记录对应门禁,再进入下一阶段:
```bash
<PYTHON> "<SKILL_DIR>/scripts/confirm_stage.py" --workdir 软件著作权申请资料 --stage <阶段名> --note "<用户确认内容>"
```
必须停住的门禁:
- `environment`:OfficeCLI 缺失时必须由用户确认全局安装并在安装后重启 Codex;版本不匹配时,用户必须切换固定版本或明确承担使用未经验证版本的风险。
- `project`:存在多个项目候选目录时,用户必须指定项目目录。
- `business`:`草稿/业务理解.md` 生成后,用户必须确认行业、目标用户、核心功能和申请口径。
- `application-fields`:`草稿/申请表信息.md` 生成后,用户必须补全并确认硬件、系统环境、著作权人、日期等字段。
- `code-selection`:`草稿/代码文件选择.json` 生成后,用户必须确认或修改抽取文件。
- `screenshot-method`:操作手册截图前,用户必须在 Playwright CLI 自动截图、用户自行截图两种方式中选择一种;如果用户明确说“现在不截图/先跳过截图”,记录为 `skip`。
- `markdown`:全部 Markdown 草稿完成后,用户必须确认可以进入 Word/TXT 生成。
## 工作流
### 1. 启动环境检查
一开始先在当前工作目录创建输出目录并检查运行能力:
```bash
<PYTHON> "<SKILL_DIR>/scripts/check_environment.py" \
--out-dir 软件著作权申请资料
```
输出:
- `软件著作权申请资料/环境检查.md`
- `软件著作权申请资料/环境检查.json`
环境检查必须告诉用户:
- 当前会在“当前目录/软件著作权申请资料”下生成材料。
- Markdown 草稿、TXT、OfficeCLI DOCX、OpenXML 校验和预览是否可用。
- 当前 OfficeCLI 路径、版本,以及是否等于固定验证版本 `1.0.151`。
- 如 OfficeCLI 缺失,询问用户是否使用官方命令全局安装;不得下载到项目目录或 skill 目录,也不得静默安装。
- 如官方全局安装已完成但当前进程尚未识别,必须要求用户重启 Codex,停止当前执行,重启后重新运行环境检查。
用户选择:
- 如果用户愿意安装,在 Windows PowerShell 中运行 `irm https://raw.githubusercontent.com/iOfficeAI/OfficeCLI/main/install.ps1 | iex`。安装完成后要求用户重启 Codex;不得在当前任务中假定 PATH 已刷新后继续执行。
- 重启后先运行 `officecli --version`,再重新运行环境检查。只使用 PATH 中的全局命令,不使用 `OFFICECLI_PATH`、`--officecli` 或项目内 `工具/officecli.exe`。
- 如果用户坚持使用其他版本,必须先记录 `environment` 门禁,正式生成时显式传入 `--allow-untested-officecli`。
- 没有可用 OfficeCLI 时只能继续生成/修改 Markdown 草稿和 TXT,不得生成伪成功的 DOCX。
用户回复后记录门禁:
```bash
<PYTHON> "<SKILL_DIR>/scripts/confirm_stage.py" \
--workdir 软件著作权申请资料 \
--stage environment \
--note "<用户选择>"
```
不要等到最后验证阶段才发现 OfficeCLI 不可用;这个信息必须在流程开始时给出。
### 2. 定位项目
用户通常会把项目放在当前文件夹下。先扫描当前目录,避开本 skill、自身输出目录、`node_modules`、构建产物和隐藏目录,找到最可能的项目根目录。
如果有多个候选项目,必须停止并询问用户选择;如果只有一个明显候选项目,可以直接使用。
### 3. 分析项目
运行:
```bash
<PYTHON> "<SKILL_DIR>/scripts/analyze_project.py" \
--project <项目目录> \
--out 软件著作权申请资料/analysis/project.json
```
分析内容包括:
- `package.json`、README、脚本命令、依赖
- 前端框架和主要编程语言
- 入口文件、路由、页面、组件、接口、状态管理
- 源码文件数量和源程序行数
- 软件名称候选、主要功能候选、运行命令候选
### 4. 形成业务理解
在写申请表和操作手册前,先让脚本收集项目证据:
```bash
<PYTHON> "<SKILL_DIR>/scripts/generate_business_context.py" \
--project <项目目录> \
--analysis 软件著作权申请资料/analysis/project.json \
--software-name "<软件全称>" \
--out-dir 软件著作权申请资料/草稿
```
输出:
- `草稿/业务理解证据.md`
- `草稿/业务理解证据.json`
- `草稿/业务理解模型稿模板.json`
这一步只收集证据,不决定最终业务口径。接下来必须由模型阅读 `业务理解证据.md/json`、README、PRD/BRD、页面文案、路由、接口、必要源码和用户补充资料,自行判断:
- 应该重点读取哪些文档和源码
- 软件属于什么行业 / 领域
- 目标用户是谁
- 核心价值是什么
- 哪些功能应写入软著申请资料
- 典型操作流程如何组织
- 操作手册适合采用什么章节结构
- 申请表建议口径如何表达
模型不得用脚本关键字表决定行业、功能和结构;不得把用户给的范本文案、测试项目名称、测试项目流程写成通用规则。
模型完成研判后,生成一个业务理解模型稿 JSON,字段至少包含:
- `product_positioning`
- `industry`
- `target_users`
- `core_value`
- `business_features`
- `business_feature_details`
- `operation_flow`
- `application_purpose`
- `main_functions`
- `technical_characteristics`
- `manual_sections`
- `manual_modules`
- `system_requirements`
- `faq`
- `glossary`
其中 `manual_modules` 是操作手册的核心输入,必须按真实页面、导航入口或业务流程填写。脚本不得按 `auth/query/form` 等分类模板自动补入口、步骤或反馈;缺少 `manual_modules` 或关键字段时必须停止让模型回到项目证据中补写。每个模块必须包含:
- `title`:页面或流程名称。
- `evidence`:对应页面、路由、组件、需求文档或 README 证据。
- `purpose`:该页面在软件中的用途。
- `usage` 或 `usage_scenario`:用户在什么业务场景下会使用该页面,正在处理什么具体事务。缺少时不得生成操作手册。
- `entry`:用户从哪里进入该页面。
- `visible_elements`:用户实际能看到的输入框、按钮、列表、标签、状态或结果区域。
- `operation_steps`:按真实页面顺序写用户动作,不能写代码实现。
- `validation_rules`:必填项、长度限制、权限、额度、状态、异常提示等规则;没有则留空数组。
- `feedback`:操作完成后用户能看到的结果、提示或状态变化。
- `screenshot`:截图预留说明。
`manual_sections` 只允许补充当前软件本身的用途、业务场景、页面组织或用户流程,不要写“本操作手册用于……”“面向软著审核……”“不描述代码实现……”这类解释文档写作方式的元话语。最终操作手册应像真实软件说明书,而不是生成过程说明。
然后运行:
```bash
<PYTHON> "<SKILL_DIR>/scripts/generate_business_context.py" \
--project <项目目录> \
--analysis 软件著作权申请资料/analysis/project.json \
--software-name "<软件全称>" \
--out-dir 软件著作权申请资料/草稿 \
--model-context <模型生成的业务理解JSON>
```
输出:
- `草稿/业务理解.md`
- `草稿/业务理解.json`
最终业务理解必须覆盖:
- 产品定位
- 面向领域 / 行业
- 目标用户
- 核心价值
- 主要业务功能
- 典型操作流程
- 申请表建议口径
- 证据来源
- 操作手册结构建议
如果项目材料不足、业务类型较新,或用户明确希望参考竞品,可联网搜索相近产品和行业资料;外部调研只用于理解行业表达,不能编造项目不存在的功能。调研摘要应写入业务理解草稿,并区分“项目证据”和“行业参考”。
生成 `业务理解.md/json` 后必须停止,等待用户确认或修改。业务理解确认前,不得生成申请表和操作手册。如果业务理解仍不充分,先请用户Discussion
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
From GitHub
- GitHub stars
- 6,366
- Maker
- Fokkyp
- License
- AGPL-3.0
- Last code change
- Oct 23, 2026
- SKILL.md files in the repo (including translated copies and templates)
- 1