Skip to content

yonglun/dama-skill / skills/managing-data-projects

managing-data-projects

Verified

Use when a data initiative spans multiple data-management domains, when the correct DAMA knowledge areas or delivery order are unclear, or when a cross-domain project plan, readiness assessment, roadmap, stage gate, or governance coverage check is needed.

templates/delivery-pack.en.md

View on GitHub
# Data Project Delivery Pack

Skill: `managing-data-projects`

[Word report](report.en.docx) · [Excel register](register.en.xlsx)

## Record details

| ID | Field | Project value |
| --- | --- | --- |
| `artifact_id` | Artifact ID | |
| `project` | Project | |
| `skill` | Skill | |
| `version` | Version | |
| `date` | Date | |
| `status` | Status | |
| `author` | Author | |
| `owner` | Owner | |
| `approver` | Approver | |
| `purpose` | Purpose | |
| `business_outcome` | Business outcome | |
| `scope` | Scope and exclusions | |
| `source_inputs` | Inputs and sources | |
| `assumptions` | Assumptions and constraints | |
| `decisions` | Decisions | |
| `rationale` | Rationale | |
| `risks` | Risks | |
| `exceptions` | Exceptions | |
| `open_items` | Open items | |
| `due_date` | Due date | |
| `acceptance_criteria` | Acceptance criteria | |
| `evidence_location` | Evidence location | |
| `reviewer_decision` | Reviewer decision | |
| `next_gate` | Next stage gate | |

## Domain analysis and decisions

### Business outcome (`business_outcome`)

Identify the decision or process to improve, beneficiaries, and how the outcome will be observed.

> Enter project evidence, conclusion, and owner.


### Scope and tailoring (`scope`)

List included and excluded domains and systems, with triggers for reconsidering exclusions.

> Enter project evidence, conclusion, and owner.


### Assumptions and constraints (`assumptions`)

Separate verified facts, working assumptions, and open questions that could change the plan.

> Enter project evidence, conclusion, and owner.


### Domain route (`domain_route`)

Classify primary, foundational, and supporting domains, with reasons for inclusion and exclusion.

> Enter project evidence, conclusion, and owner.


### Activities and dependencies (`dependencies`)

Sequence prerequisite decisions and Plan, Control, Develop, and Operate activities.

> Enter project evidence, conclusion, and owner.


### Roles and decision rights (`decision_rights`)

Name one accountable role per key decision and any risk veto authority.

> Enter project evidence, conclusion, and owner.


### Risks and controls (`risks_controls`)

Record risk events, controls, thresholds, escalation deadlines, and residual-risk approval.

> Enter project evidence, conclusion, and owner.


### Deliverables and acceptance evidence (`acceptance_evidence`)

For each work package, specify a reviewable artifact, acceptance method, and evidence location.

> Enter project evidence, conclusion, and owner.


### Next stage gate (`next_gate`)

State exit criteria for Go, Conditional Go, Hold, Rework, or Stop.

> Enter project evidence, conclusion, and owner.


## Working registers

### Work Packages (`work_packages`)

Track how domain work contributes to business outcomes.

| Domain (`domain`) | Goal (`goal`) | Owner (`owner`) | Dependency (`dependency`) | Deliverable (`deliverable`) | Acceptance evidence (`acceptance_evidence`) | Status (`status`) |
| --- | --- | --- | --- | --- | --- | --- |
|   |   |   |   |   |   |   |

### Risks and Controls (`risks`)

Record risk events, controls, and escalation responsibility.

| Risk event (`event`) | Impact (`impact`) | Control (`control`) | Threshold (`threshold`) | Owner (`owner`) | Escalation (`escalation`) | Evidence (`evidence`) |
| --- | --- | --- | --- | --- | --- | --- |
|   |   |   |   |   |   |   |

### Stage Gates (`gates`)

Record gate exits, evidence, and approval decisions.

| Stage (`stage`) | Exit criteria (`exit_criteria`) | Evidence (`evidence`) | Decision (`decision`) | Approver (`approver`) | Date (`date`) |
| --- | --- | --- | --- | --- | --- |
|   |   |   |   |   |   |
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall