Artifact Pack Generator

# Artifact Pack Generator

## Purpose

Generate a first-pass markdown artifact pack for a consulting or
software delivery engagement.

Use this only after the team has separated facts from assumptions. Do
not invent evidence to make an artifact look complete.

## Inputs

Use one or more of:

- Engagement context summary.
- Engagement path recommendation.
- Discovery gap report.
- Source notes, transcripts, and documents.
- Existing client artifacts.

## Artifact types

Generate only the artifacts that are useful for the engagement stage:

- Kickoff brief.
- Current-state summary.
- Initial risk register.
- Decision log.
- 30/60/90 roadmap.
- System or service inventory.
- Executive summary.

Each artifact must include an owner, audience, source evidence, and
update path.

## Process

1. Select the smallest useful artifact set.
2. For each artifact, identify audience and decision it supports.
3. Populate only claims supported by evidence.
4. Mark assumptions and gaps inline.
5. Add owner and update path.
6. Recommend which artifact should be reviewed first.

## Output format

```markdown
# Engagement Artifact Pack

## Artifact inventory

| Artifact | Audience | Owner | Update path |
| -------- | -------- | ----- | ----------- |
|          |          |       |             |

## Kickoff brief

Audience:
Owner:
Source evidence:
Update path:

### Summary

### Outcomes

### Scope and non-goals

### Known risks

### Immediate next steps

## Current-state summary

Audience:
Owner:
Source evidence:
Update path:

### Systems and services

### Delivery workflow

### Operations and support

### Open questions

## Initial risk register

| Risk | Impact | Evidence | Owner | Next action |
| ---- | ------ | -------- | ----- | ----------- |
|      |        |          |       |             |

## Decision log

| Decision | Status                  | Owner | Evidence | Next step |
| -------- | ----------------------- | ----- | -------- | --------- |
|          | Needed / Made / Blocked |       |          |           |

## 30/60/90 roadmap

### First 30 days

### Days 31-60

### Days 61-90

## Review order

1. Artifact:
   Why first:
```

## Quality bar

- Do not fill blanks with generic best practices.
- State when evidence is missing.
- Keep artifacts short enough for humans to review.
- Prefer fewer, stronger artifacts over a large weak packet.
- Make ownership and maintenance explicit.