Skip to content
Back to skills

Paw Ps Product Package Assembler

ASecurity

Bundle product artifacts into a coherent, production-ready package. Use when the user requests 'package product', 'bundle artifacts', 'assemble deliverables', 'create product package', or 'finalize outputs'.

  • 116 stars
  • 0 votes
  • 0 copies
  • 5 views
  • Added September 10, 2026
researchgodocumentation

Security analysis

A100/100

Pro scans all 5 files and shows the line behind each finding

Scanned November 9, 2026

npx -y skills add pawbytes/skill-suites --skill paw-ps-product-package-assembler --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Paw Ps Product Package Assembler?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Paw Ps Product Package Assembler
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/pawbytes-paw-ps-product-package-assembler/badge)](https://www.skillsdirectory.com/skills/pawbytes-paw-ps-product-package-assembler)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: paw-ps-product-package-assembler
description: Bundle product artifacts into a coherent, production-ready package. Use when the user requests 'package product', 'bundle artifacts', 'assemble deliverables', 'create product package', or 'finalize outputs'.
---

# Product Package Assembler

## Overview

This workflow bundles product artifacts from the execution phase into a coherent, production-ready package. It ensures outputs feel like one unified product, not scattered drafts, by gathering executor outputs, verifying completeness against product-type requirements, organizing into a structured bundle, and generating a comprehensive manifest.

**Args:** Accepts `--headless` / `-H` for non-interactive execution.

**Output:** Packaged product bundle with organized directory structure, completeness report, and packaging manifest.

**The Non-Negotiable:** Must ensure outputs feel like one product, not scattered drafts.

## Path Resolution

- `{suite-root}` is `root` from `uv run {skill-root}/scripts/paw-paths.py detect` (`{skill-root}` is this skill's folder), normally `{project-root}/paw-suites/products`. All paths below are relative to it. A custom folder in config `ps.products_folder` (or `ps.memory_folder` for `_memory/`) wins (`detect` lists it under `overrides`; an old default is not one).
- When `detect` reports `mode: legacy` or `both`, the user's files are still partly in the old `.pawbytes/prodig-suites/` tree. Pass every path through `paw-paths.py locate <path>` (add `--write` for a new file) and use the path it returns. Once per session, tell the user that `paw-ps-setup` can move them to `paw-suites/products/`, and offer it. Keep working either way.

## On Activation

Load available config from `{project-root}/.pawbytes/config/config.yaml` and `{project-root}/.pawbytes/config/config.user.yaml` (root level and `ps` section). If config is missing, let the user know `paw-ps-setup` can configure the module at any time. Resolve:

- `{user_name}` (null) — address the user by name
- `{communication_language}` (English) — use for all communications
- `{document_output_language}` (English) — use for generated document content

Load shared memory from `{suite-root}/_memory/index.md`. Load output standards from `{suite-root}/_standards/output-standards.md`.

**Product context resolution:** Identify the active product from memory or accept a product slug as argument. The product workspace is expected at `{suite-root}/{product-slug}/`. If no product can be resolved, ask the user.

If `--headless` or `-H` is passed, run the full pipeline without interaction: gather artifacts, check completeness, organize bundle, generate manifest.

Otherwise, greet the user, confirm the target product, and proceed through the stages below.

## Pipeline

This workflow progresses through four stages. Each stage updates the packaging status file using the document-as-cache pattern for compaction survival.

| Stage | Purpose | Reference |
|-------|---------|-----------|
| 1. Gather Artifacts | Collect all execution artifacts from executors | Load `./references/01-gather-artifacts.md` |
| 2. Check Completeness | Verify against product-type requirements | Load `./references/02-check-completeness.md` |
| 3. Organize Bundle | Structure into coherent package | Load `./references/03-organize-bundle.md` |
| 4. Generate Manifest | Create package manifest and notes | Load `./references/04-generate-manifest.md` |

**Progression:** Each stage updates `packaging-status.md` with its results before loading the next stage. If interrupted, resume from the last completed stage by reading `packaging-status.md`.

## Packaging Status File

All progress is written to `{suite-root}/{product-slug}/packaging-status.md`. This file is both the output artifact and the recovery cache.

```yaml
---
product: '{product-slug}'
status: 'in-progress'  # pending | in-progress | complete | incomplete
current_stage: '01-gather-artifacts'
created: 'ISO-8601'
updated: 'ISO-8601'
artifacts_found: 0
artifacts_packaged: 0
missing_items: []
---
```

## Artifact Sources

Artifacts are collected from the product folder: executor outputs in `{suite-root}/{product-slug}/build/`, plus `plan/`, `research/`, `audience/` and the product brief.

| Source | Contains | Manifest File |
|--------|----------|---------------|
| Discovery agents | Research reports, briefs, specs | `discovery-manifest.json` |
| Strategist | Strategy documents, plans | `strategy-manifest.json` |
| Executor agents | Content, code, designs, media | `executor-manifest.json` |
| Synthesis workflows | Integrated deliverables | `synthesis-manifest.json` |

## Product Types & Completeness Criteria

Different product types have different required artifacts:

| Product Type | Required Artifacts |
|--------------|-------------------|
| Document | Main document, outline, research notes |
| Application | Code package, README, documentation |
| Campaign | Creative assets, copy, strategy brief |
| Report | Report document, data sources, methodology |
| Presentation | Slide deck, speaker notes, handouts |

## Output Structure

```
{suite-root}/{product-slug}/package/
├── manifest.json           # Package manifest
├── completeness-report.md  # What's present, what's missing
├── packaging-notes.md      # Special considerations
├── artifacts/              # All gathered artifacts
│   ├── {artifact-1}
│   ├── {artifact-2}
│   └── ...
└── metadata/               # Supporting metadata
    ├── source-manifests/
    └── audit-trail.json
```

## Memory Contract

**Reads:**
- `{suite-root}/_memory/index.md` — module state
- `{suite-root}/_standards/output-standards.md` — output standards
- `{suite-root}/{product-slug}/product-context.md` — product context
- Executor manifests from execution phase

**Writes:**
- `{suite-root}/{product-slug}/packaging-status.md` — packaging progress
- `{suite-root}/{product-slug}/package/` — packaged bundle
- `{suite-root}/_memory/daily/{date}.md` — daily log (append, tagged `[Packaging]`)
- `{suite-root}/{product-slug}/README.md` — set `Status: packaged` (or `packaging incomplete`), `Next:` (usually `paw-ps-publish-ready-check`) and link `package/manifest.json`; then run `uv run {skill-root}/scripts/paw-paths.py index`

## Escalation Routes

| Signal | Routes To |
|--------|-----------|
| Missing executor outputs | paw-ps-agent-product-builder (to rerun execution) |
| Incomplete artifacts | Appropriate executor agent |
| Quality issues | paw-ps-quality-reviewer |
| Export needs | paw-ps-export-handler |

## Output Contract

Every packaging deliverable includes:

- **Action type:** bundling, completeness-check, organizing
- **Files saved:** paths to all created files
- **Completeness status:** what's present vs. missing
- **Recommendations:** next steps (quality review, re-execution, etc.)
- **Package location:** resolved path to bundle

Files in this skill

  • SKILL.md6 KB
  • references/01-gather-artifacts.md3 KB
  • references/02-check-completeness.md3.7 KB
  • references/03-organize-bundle.md3.8 KB
  • references/04-generate-manifest.md6 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in research →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.