一键在 Manus 中运行任何 Skill

qingsong-doorstop

星标4

分支0

更新时间2026年2月24日 14:32

Specialized knowledge for managing MUST requirements, risks, and interfaces using the Qingsong wrapper around Doorstop. Use when creating, updating, or analyzing the requirements network (REQ, RSK, IFC, DOC, DAT, NOTE).

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

dr-guangtou

dr-guangtou/guangtou_vibe

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Qingsong Doorstop Management

This skill provides expert guidance for the "Requirements as Code" workflow used in the MUST project.

1. Domain Knowledge

1.1 Item ID Pattern

All items must follow: MUST-<L1>-<L2>-<TYPE>-NNN

<L1>: Major system (FPS, SPS, DMS, SWG)
<L2>: Subsystem (FID, DET, PIPE, etc.)
<TYPE>: REQ, RSK, IFC, DOC, DAT, NOTE
<NNN>: 3-digit sequence

1.2 Hierarchy & L3

Items are stored in doorstop/<TYPE>/<L1>/<L2>/.
For complex sub-assemblies, a deeper path is allowed: doorstop/<TYPE>/<L1>/<L2>/<L3>/.
L3 items are first-class items with their own requirements and verification.

1.3 Link Types & Rules

Link Type	Semantic Meaning	Source -> Target
`implements`	Satisfies a requirement	DOC, DAT, NOTE -> REQ
`verifies`	Provides verification evidence	DOC, DAT, NOTE -> REQ
`mitigates`	Risk mitigation	NOTE, DOC, REQ -> RSK
`impacts`	Risk impact area	RSK -> REQ, IFC, DOC
`derives_from`	Hierarchical link	REQ -> REQ

2. Workflows

2.1 Creation

Verify the <L1>/<L2> path in meta/hierarchy.yaml.
Determine the next available sequence number.
Use the qingsong new CLI or QingsongCore.create_item API.
Ensure owner is a valid ID from meta/people.yaml.

2.2 Refactoring (Conceptual Design Phase)

When moving or merging systems:

Update meta/hierarchy.yaml.
Move files to the new directory structure.
Update IDs in the YAML files.
Critical: Search the entire repository for the old ID and update any links to point to the new ID.

2.3 Validation

Always run qingsong validate after any edit.

No circular dependencies allowed in derives_from links.
All link targets must exist in the repository or be marked EXT:.
All owners and system paths must exist in meta/.

3. Storage Architecture

Source of Truth: YAML files in doorstop/.
Query Engine: SQLite cache in index/qingsong.sqlite.
Update Cycle: Edit YAML -> Validate -> Rebuild Cache.

同仓库更多 Skills

同仓库

galfit

dr-guangtou/guangtou_vibe

Guidance and a bundled round-tripping parser for the GALFIT 2-D galaxy image-fitting code (Peng 2002/2010). Use when the task involves GALFIT input/output files (`.galfit`, `.feedme`, `galfit.NN` restart files), GALFIT constraint files, invoking the GALFIT binary, converting GALFIT configs to or from YAML/JSON, or questions about GALFIT profile parameters (sersic, nuker, moffat, king, ferrer, edgedisk, expdisk, devauc, gaussian, psf, sky) and hidden blocks (C0 diskyness/boxyness, Fourier modes, bending modes, coordinate rotation R0-R10, truncation T0-T10).

2026-04-194

hybrid-cascade-investigation

dr-guangtou/guangtou_vibe

Systematic multi-agent workflow combining quick redundancy scanning with targeted deep dives for comprehensive research coverage

2026-04-044

autoprof

dr-guangtou/guangtou_vibe

AutoProf non-parametric galaxy isophote fitting pipeline. Use when fitting galaxy surface brightness profiles with AutoProf's FFT-based method, benchmarking against photutils/GALFIT, or running AutoProf programmatically on FITS images.

2026-04-024

pysersic

dr-guangtou/guangtou_vibe

Bayesian Sérsic profile fitting for galaxy photometry using JAX/NumPyro. Use when fitting galaxy surface brightness profiles, extracting structural parameters, or performing multi-component galaxy decomposition.

2026-04-024

stilts-cli

dr-guangtou/guangtou_vibe

STILTS (Starlink Tables Infrastructure Library Tool Set) - Command-line tools for processing astronomical tabular data

2026-04-014

hsc-survey-data

dr-guangtou/guangtou_vibe

Access Hyper Suprime-Cam (HSC) Subaru Strategic Program (SSP) survey data using official tools

2026-03-314

name	qingsong-doorstop
description	Specialized knowledge for managing MUST requirements, risks, and interfaces using the Qingsong wrapper around Doorstop. Use when creating, updating, or analyzing the requirements network (REQ, RSK, IFC, DOC, DAT, NOTE).

Qingsong Doorstop Management

This skill provides expert guidance for the "Requirements as Code" workflow used in the MUST project.

1. Domain Knowledge

1.1 Item ID Pattern

All items must follow: MUST-<L1>-<L2>-<TYPE>-NNN

<L1>: Major system (FPS, SPS, DMS, SWG)
<L2>: Subsystem (FID, DET, PIPE, etc.)
<TYPE>: REQ, RSK, IFC, DOC, DAT, NOTE
<NNN>: 3-digit sequence

1.2 Hierarchy & L3

Items are stored in doorstop/<TYPE>/<L1>/<L2>/.
For complex sub-assemblies, a deeper path is allowed: doorstop/<TYPE>/<L1>/<L2>/<L3>/.
L3 items are first-class items with their own requirements and verification.

1.3 Link Types & Rules

Link Type	Semantic Meaning	Source -> Target
`implements`	Satisfies a requirement	DOC, DAT, NOTE -> REQ
`verifies`	Provides verification evidence	DOC, DAT, NOTE -> REQ
`mitigates`	Risk mitigation	NOTE, DOC, REQ -> RSK
`impacts`	Risk impact area	RSK -> REQ, IFC, DOC
`derives_from`	Hierarchical link	REQ -> REQ

2. Workflows

2.1 Creation

Verify the <L1>/<L2> path in meta/hierarchy.yaml.
Determine the next available sequence number.
Use the qingsong new CLI or QingsongCore.create_item API.
Ensure owner is a valid ID from meta/people.yaml.

2.2 Refactoring (Conceptual Design Phase)

When moving or merging systems:

Update meta/hierarchy.yaml.
Move files to the new directory structure.
Update IDs in the YAML files.
Critical: Search the entire repository for the old ID and update any links to point to the new ID.

2.3 Validation

Always run qingsong validate after any edit.

No circular dependencies allowed in derives_from links.
All link targets must exist in the repository or be marked EXT:.
All owners and system paths must exist in meta/.

3. Storage Architecture

Source of Truth: YAML files in doorstop/.
Query Engine: SQLite cache in index/qingsong.sqlite.
Update Cycle: Edit YAML -> Validate -> Rebuild Cache.