skills.rest
qiusuo0226
qiusuo0226COMMUNITY
Explore all skills by this author →
GitHub

chrono-pm-source-split

Documents the capability boundary for splitting source documents into structured requirement directories.

4|Updated Aug 21, 2026
Search Tags:#project management#markdown#capability boundary#migration checklist#requirement splitting#source document
One-click install
npx skills add https://github.com/qiusuo0226/chrono-pm-skill --skill chrono-pm-source-split-qiusuo0226
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: chrono-pm-source-split
Source: https://github.com/qiusuo0226/chrono-pm-skill/tree/main/governance-shared/baselines/3.7.0/ChronoPM-Project/source-split-skill
Command: npx skills add https://github.com/qiusuo0226/chrono-pm-skill --skill chrono-pm-source-split-qiusuo0226

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Project managers need a clear map of which rules, templates, and tests govern the source-document splitting capability inside ChronoPM-Project, so the capability can later be extracted into a standalone package without breaking REQ/WP bindings or cross-project source recognition. ## Core Features & Use Cases - Capability Boundary Manifest: Lists every rule file, template, and regression test module that belongs to the source-document splitting capability (meta/_digest/atoms/facts/ledger/parse-log six-piece output). - Migration Checklist: Defines the future extraction steps and the only allowed cross-module touchpoints (REQ/WP numbering and glossary term intake). - Use Case: A maintainer planning to spin the splitting capability out of ChronoPM-Project consults this manifest to know exactly which sections of references 05, 06, 07, 14, 17, 18, 19, and 20 plus which templates and regression modules must move. ## Quick Start Ask the AI to show the capability boundary and migration checklist for the source-document splitting feature before refactoring it into a standalone package.

Frequently Asked Questions about chrono-pm-source-split

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What does the source document splitting capability produce?▼

It splits a source document into a six-piece directory under requirements/sources/{id}/ containing meta, _digest, atoms, facts, ledger, and parse-log files. These artifacts support REQ-to-WP binding and cross-project recognition of shared sources.

Is this directory a loadable Skill at runtime?▼

No. The SKILL.md explicitly states it is a manifest file, not a runtime loading entry point, and hosts must not discover it as an independent Skill. The authoritative rules remain in the ChronoPM-Project references files.

Which rule files govern source document splitting in ChronoPM?▼

The boundary manifest lists references 07 (requirement rules sections 8.6 through 8.14), 05 (query routing and reconciliation), 06 (file sharding and parse-log archiving), 14, 17, 18, 19, and 20, plus five source templates and regression modules 53 and 54.

What dependencies are allowed when extracting the splitting capability?▼

The splitting capability must not depend on unrelated modules like daily reports or todos. The only permitted cross-points are the REQ/WP numbering system and glossary term intake defined in reference 17.

How do I migrate the splitting feature into a standalone package?▼

Follow the four-step checklist in references/capability-boundary.md: extract the listed rule sections as package references, move the five templates, leave REQ/WP cross-point pointers in ChronoPM-Project, then convert the SKILL.md into a real loading entry.

Related Skills

Explore More Product & Management Skills→
Douglas-vDouglas-v

wiki-ingest

Converts raw source documents into interlinked, cited wiki pages with contradiction tracking.

Community
Intermediate
SteveGJonesSteveGJones
41

req-add

Mint a new REQ ID and append it to the requirements-spec.

Community
Intermediate
joaopelegrinojoaopelegrino

ux-nomenclature

Enforce glossary-approved UX terms in React components and data files.

Community
Basic
JoyJoin-Tech-LimitedJoyJoin-Tech-Limited

process-refactoring

Guides incremental behavior-preserving code refactoring with typecheck and test verification.

Official
Intermediate