SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillsoneos-autoprd

oneos-autoprd

Office & productivity

View repository

Updated 10-15 08:53

About this skill

AutoPRD（oneos-autoprd）

Generate for OneOS business modulesproduct-manager-readable, reviewable, schedulablerequirement descriptions, andautomatically attach them to Axhub Make annotation tool → prototype directory。

Also supports: duringThis Round Finalization / Requirement Finalizationaggregating feature changes andautomatically incrementing the PRD version number; when combined with $YunxiaoPM , upondesign completion(or explicit delivery sync) write the Markdown into the [Delivery] task description.

Old package yunxiao-requirement-lifecycle has been removed from the marketplaceDo not load it. The Yunxiao state machine and the [Delivery]/[Analysis]/[Design] treeare onlyhandled by YunxiaoPM; this Skill does notcreate same-named stage tasks without a prefix.

Granularity: clearly explain what to do, who uses it, story points, forward and reverse, flowcharts, and key business logic;do not writetable structures, interfaces, field code names, file paths, or implementation lists.

When to use (including automatic triggering)

Proactive invocation

  • AutoPRD, OneOS requirements description, whole-module PRD, story points + flowchart, product description

Must automatically follow up when prototypes change

  • Modify src/prototypes/<id>/ pages, interactions, copy, decision logic, and acceptance-related content
  • In the same round, synchronously update the PRD Markdown + annotation directory;pure styling with no product-semantic changes may skip the full rewrite

At requirement finalization (mandatory)

Combined with YunxiaoPM (mandatory · the only Yunxiao combination)

  • Design completion or refining the "product description": first this Skill writes the MD to disk, then YunxiaoPM / this Skill writes the requirement according to yunxiao-description.md , ## 产品说明（AutoPRD）（does not overwrite ## 原始诉求（AutoRDO） / ## 工作项编号（系统））
  • When creating [Delivery], do not write the PRD body(the placeholder is written by YunxiaoPM); upon design completion or the command "sync delivery description", use the task yunxiao-delivery-sync.md according tonumberto backfill [Delivery]
  • Chat/recording cleanup before ingestion: first $AutoRDO, then YunxiaoPM records the requirement

Cross-Skill logic handoff (mandatory)

  • Only pass to YunxiaoPM the formal Skill name, requirement/delivery task number, PRD version, body or object-storage evidence identifier; installation locations must not be passed.
  • It is forbidden to locate or read other Skills' installation directories. Each Skill reads only resources within its own package; when Yunxiao context is missing, query in real time by number or require the upstream to supply the logic handoff fields.
  • The next hop may only output the formal selector $YunxiaoPM。

Workflow

Main process (write/sync PRD)

  1. Determine module: OneOS module name and src/prototypes/<prototype-id>/。

  2. Read context (product semantics only)

    • user description, confirmed definitions, prototype annotations,.spec/, business line description (lines.ts）
    • ignore implementation details; rewrite field names/interfaces into business language.

  3. Convergence boundary: what to do / what not to do, external dependencies, relationships with other modules.

  4. Write according to the template: see "Output structure" and references/template.md。

  5. Persist to disk + annotation sync (mandatory) — references/annotation-sync.md。

    Order Action
    A Write/update src/prototypes/<id>/.spec/requirements-prd.md
    B Write/update src/resources/prd/<id>-autoprd.md
    C Update annotation-source.json top-level directory.nodes(full PRD + recommended chapter breakdown)
    D If scripts/sync-annotation-directory.mjsexists, execute it

  6. Delivery notes: paths, annotation entry points, total story points, open questions/assumptions.

Finalization process

See references/release-changelog.md. Includes automatic V主.副.子；When the user explicitly specifies primary/secondary/sub, the user's specification prevails。

Yunxiao requirement "Product description" (with the YunxiaoPM two-section template)

See references/yunxiao-description.md。

Yunxiao [Delivery] backfill (design complete · not at creation time)

See references/yunxiao-delivery-sync.md。

Hard writing constraints

Must write (mapping the user summary)

Summary capability Falls under chapter
Overview §1 One sentence and goals
Goals / boundaries §1–2
Roles §3
User stories (starting point → operation → closed loop) + story points §4
Forward and reverse flows §5
Key logic / states / risks §6 (and acceptance-related)
Flowchart §7
Delivery §9 Delivery criteria
Finalization changes §10

Also: acceptance checklist §8; object storage preview link form {baseUrl}/{prototype-id}/index.html(adding the prototypes/ prefix is prohibited, removing index.html）。

Prohibited content

  • Database tables, field names, interface paths, code paths, component names, storage keys
  • Style/UI/table structure optimization in the change log
  • Guidance to load a delisted lifecycle or create a task with the same-named stage

User story criteria (mandatory · aligned with the business line description)

Source of truth: business line description (lease-business-line-overview / lines.ts）。
Main narrative:starting point → how it operates → closed loop(do not use the "As a… I want…" wide table as the main narrative).

Output structure

Full template:references/template.md。

# <模块名> · 产品需求说明（全模块）

## 1. 一句话与目标
## 2. 模块边界（最重要）
## 3. 用户与角色
## 4. 用户故事与故事点（业务条线说明口径）
## 5. 功能模块说明（正向 / 逆向）
## 6. 关键业务逻辑（必须对齐）
## 7. 总览流程图
## 8. 验收清单
## 9. 交付口径
## 10. 功能变更记录   ← 定稿维护；含 V主.副.子

Quality self-check

  • Product managers can review without reading code
  • User stories are starting point / how it operates / closed loop
  • .spec/requirements-prd.md + annotation directory synchronized
  • At finalization: Chapter 10 includes the version number + autoprd-baseline.json includes prdVersion
  • and YunxiaoPM design complete: [Delivery] according tonumberbackfill; at creation time MD is not pre-loaded
  • The full text contains no guidance to load a delisted lifecycle; no task creation with the same-named stage
  • The change log contains no style/UI/table structure filler

Reference