skills.rest
ginmp8
ginmp8COMMUNITY
Explore all skills by this author →
GitHub

sequential-work-packaging

Plan and package sequential work into canonical artifact structures.

Updated Apr 27, 2026
Search Tags:#workflow#planning#canonical#sequential-packaging#spec-catalog#mago
One-click install
npx skills add https://github.com/ginmp8/rhapsodia --skill sequential-work-packaging
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sequential-work-packaging
Source: https://github.com/ginmp8/rhapsodia/tree/main/skills/sequential-work-packaging
Command: npx skills add https://github.com/ginmp8/rhapsodia --skill sequential-work-packaging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces a planning-first workflow for sequential work packaging and aligns MAGO-style prompts to the canonical artifact layout.

Core Features & Use Cases

  • Enforce canonical sequential work packaging structure: provides a stable macro container and execution identifiers to keep planning and execution aligned.
  • Adapt MAGO prompts into canonical artifacts: maps mago modes (define, refine, decompose, order) to the canonical artifact set cycle_version/spec_id/feature_key/feature_version.
  • Audit and normalize planning artifacts: ensures presence and consistency of spec-catalog.yaml and per-spec planning files (manifest.yaml, prd.md, tasks.md, notes.md, validation.md) across specs.

Quick Start

Create or audit a spec package following the canonical layout: cycle_version/specs/specNNN with manifest.yaml, prd.md, tasks.md, notes.md, and validation.md, and update spec-catalog.yaml accordingly.

Frequently Asked Questions about sequential-work-packaging

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

FAQPage Schema
What is sequential work packaging in a planning workflow?▼

Sequential work packaging structures planning artifacts into a disciplined cycle-based spec layout, ensuring execution aligns with planning through canonical artifacts like manifest.yaml and prd.md.

How do I adapt MAGO prompts into a canonical spec structure?▼

You adapt MAGO prompts by mapping modes like define, refine, decompose, and order to canonical artifacts using cycle_version, spec_id, and feature_key identifiers for consistent planning.

How do I audit planning artifacts for missing mandatory files?▼

You audit planning artifacts by checking each spec directory for mandatory files including manifest.yaml, prd.md, tasks.md, notes.md, and validation.md, then normalizing any inconsistencies found.

Do I need a specific file layout to enforce canonical sequential packaging?▼

Yes, canonical sequential packaging requires a strict layout: cycle_version/specs/specNNN directories containing mandatory planning files, tracked centrally via a spec-catalog.yaml file.

Can I normalize existing spec catalogs without recreating the entire package?▼

Yes, you can normalize existing planning artifacts by auditing the spec-catalog.yaml and per-spec files, ensuring mandatory artifacts are present and consistent without rebuilding the structure.

What is the best way to structure work decomposition for cycle-based specs?▼

The best way to structure work decomposition is applying mode-driven workflows within the canonical artifact set, using execution identifiers to keep order, define, and refine tasks aligned.

Related Skills

Explore More Product & Management Skills→
daudaudinangdaudaudinang

lp-spec

Clarify business requirements and UX flows into a canonical spec.md artifact.

Community
Advanced
ginmp8ginmp8

mago

Generate canonical planning artifacts under BOARD_ROOT/specs/<spec_id>/ from governance intake and repository truth.

Community
Advanced
HHU3637krHHU3637kr
140

spec-review

Audit plan and summary documents against the Spec for deviations.

Community
Advanced
whatevertogowhatevertogo

openspec-explore

Explores codebases and drafts OpenSpec proposals without writing implementation code.

Community
Intermediate