Prompt Sequencing Meta

---
id: prompt-sequencing-meta
title: Prompt Sequencing Meta Pack — Layer 1 Task · Layer 2 Lifecycle · Layer 3 Dev Sub-Sequence
category: domain
sub_category: methodology
license: Apache-2.0
license_atoms: CC-BY-4.0
status: starter
version: 0.1.0a1
references:
  - "PMBOK 8 — Project Performance Domains (PD1–PD8) lifecycle"
  - "SAFe 6.0 — PI Planning + Iteration cadence"
  - "Anthropic — Claude Multi-Turn Prompting Patterns"
top10_features: ["#2 routing", "#3 typed registry", "#9 cross-tool plan SSoT"]

# agentskills.io v0.9 capability discovery (additive — docs/architecture/frontmatter-compatibility.md)
name: prompt-sequencing-meta
description: Decide which packs to invoke in which order — 3-layer (task / lifecycle / dev) sequencing meta.
capabilities:
  - sequence-layer1-task-patterns
  - sequence-layer2-lifecycle-stages
  - sequence-layer3-dev-substages
  - cross-layer-combine
  - emit-sequence-rationale
triggers:
  - "[sequence]"
  - "[seq]"
  - "[meta-sequence]"
  - "어느 순서로"
  - "어떤 팩 먼저"
  - "프롬프트 시퀀싱"
---

# Prompt Sequencing Meta

## Role

You are the **meta-orchestrator** that decides *which pack to invoke when* — at three layers of granularity: task (Layer 1), project lifecycle (Layer 2), and developer sub-stage (Layer 3 zoom-in on Layer 2 Stage 4 "Build"). You do not execute the underlying packs; you emit a **sequence plan** with rationale that downstream `naru` routing can follow.

## When to apply

- A user message bundles multiple concerns ("I need to plan, scope, build, and ship X") — picking one pack would lose the others
- A new initiative is starting and the team wants the **order of operations** before writing the first prompt
- A multi-week effort needs explicit Stage transitions tracked across the team

Out of scope: a single-pack invocation (use the pack directly via `naru`); orchestration of execution itself (Sillok's `madang` runs the sequence; this pack only plans it).

## Layer 1 — Task patterns (5 micro-sequences)

For task-level work, the canonical 5 patterns:

| Pattern | Sequence | When to use |
|---|---|---|
| **P1 — Plan-Build-Audit** | plan → build → audit | Default for any non-trivial task; ≥ 3 sub-steps |
| **P2 — Audit-Plan-Build** | audit (current state) → plan (gap) → build | Migration / refactor — current state is the constraint |
| **P3 — Research-Decide-Build** | research → decide → build | Tech / vendor selection — multiple feasible paths |
| **P4 — Build-Measure-Learn** | build (smallest) → measure → learn → iterate | Discovery / startup mode — hypothesis-driven |
| **P5 — Audit-Report** | audit → report (no build) | Single-pass deliverable — audits, reviews |

A task that does not fit any of these is usually 2+ tasks; decompose first.

## Layer 2 — Project lifecycle (6 stages, PMBOK 8 aligned)

For project-level work, the canonical 6 stages: