Contract
- Input: project brief, stakeholder map, deliverable list, timeline constraints, and quality requirements.
- Output: graphic design project management artifact with project plan, iteration schedule, review gates, and handoff standards.
- Scope: stay within the skill's declared boundaries; do not broaden without explicit direction.
- Rule: documented standards override defaults; explicit project rules take precedence.
- Rule: if blocked by missing context or dependencies, surface the blocker before proceeding.
Provenance
| Question |
Answer |
| What is the source of truth? |
The user's request, originating spec/issue, and the skill's declared outputs |
| What is in scope? |
Work covered by the skill's acceptance criteria and completion rules |
| What is explicitly out of scope? |
Files, behaviors, and decisions outside the skill's declared boundary |
| Who or what consumes this artifact afterward? |
The next skill in the workflow or the user |
| What evidence proves it is done? |
Completion criteria met, artifact saved, validation passed |
| What risk remains? |
Subjective judgment calls, missing context, or external dependency failures |
Artifact
Emit GraphicDesignProjectManagementArtifact as both:
- JSON:
.agents/skills/platform/artifacts/graphic-design-project-management/{identifier}.json
- Markdown view: same filename with
.md extension
Graphic Design Project Management
Use this skill when a graphic design project needs explicit scope, timeline, iteration cycles, review gates, and asset handoff standards. It should translate stakeholder expectations into a durable project plan that keeps quality, feedback, and delivery visible.
Steps
1. Define project scope and deliverables
- List deliverables: posters, social graphics, brand assets, packaging, editorial layouts, presentations.
- Define acceptance criteria per deliverable: format, resolution, color space, brand compliance, accessibility.
- Define out-of-scope items explicitly.
- Identify dependencies between deliverables.
Completion criterion: scope and deliverables with acceptance criteria saved.
2. Plan timeline and milestones
- Define project phases: discovery, concept, refinement, production, delivery.
- Assign estimated durations and milestone dates.
- Identify critical path and buffer time.
- Define dependencies between phases and deliverables.
Completion criterion: timeline with milestones and critical path saved.
3. Design iteration cycles
- Define iteration structure: number of rounds, feedback format, revision limits.
- Separate internal review from stakeholder review.
- Define feedback window and response time expectations.
- Specify what constitutes a new iteration versus a minor revision.
Completion criterion: iteration schedule with feedback rules saved.
4. Define review gates and approval workflow
- Define review stages: internal creative review, stakeholder review, brand review, legal review, final approval.
- Assign owner and approver per gate.
- Define approval criteria per gate.
- Define escalation path for blocked approvals.
Completion criterion: review gates with owners, approvers, and criteria saved.
5. Specify asset handoff standards
- Define required formats per deliverable: source files, exported files, preview files.
- Define naming conventions: project code, deliverable type, version, date.
- Define folder structure and asset organization.
- Define versioning strategy: semantic versioning or date-based versioning.
- Define documentation requirements: readme, font licenses, color values, production notes.
Completion criterion: asset handoff standards saved.
6. Document quality gates
- Define quality checks per deliverable: brand compliance, accessibility, resolution, color accuracy, spelling.
- Define who performs each check.
- Define pass/fail criteria.
- Define rework process for failed quality gates.
Completion criterion: quality gate checklist with owners and criteria saved.
7. Plan stakeholder communication
- Define meeting cadence: standup, review, retro.
- Define communication channels: async updates, synchronous reviews.
- Define escalation path for blockers.
- Define retrospective schedule and format.
Completion criterion: stakeholder communication plan saved.
Completion
- the skill's completion criteria are explicitly checked
- the artifact is saved and validated
- any blockers or skipped validations are documented
- the next consumer is identified or the work is handed off
@include .agents/skills/platform/contract-base.xml
1---2name: "graphic-design-project-management"3category: "graphic-design"4maturity: "experimental"5version: "1"6description: "Manage graphic design projects — briefs, iterations, reviews, asset handoff, versioning, and delivery — with explicit scope, timelines, and quality gates."7license: "MIT"8capabilities:9 - apply graphic design project management methods within explicit graphic-design boundaries10 - analyze manage graphic design projects — briefs, iterations, reviews, asset handoff, versioning, and delivery — with explicit scope, timelines, and quality gates with assumptions, constraints, and failure modes11 - produce and validate a graphic-design artifact with evidence, decisions, and next steps12outputs: "graphic design project management artifact with project plan, iteration schedule, review gates, and handoff standards."13sideEffects: ""14dependencies: []15stopCondition: "Graphic design project management plan complete; scope, timeline, iterations, reviews, and handoff standards explicit."16risk: "low"17trustTier: "2"18maxIterations: "6"19promptVersion: "2.0"20artifactType: "plan"21modelTier: "fast"22evaluators: ["behavioral", "regression"]23fixturesPath: ""24diataxis: "how-to"25tags: ["graphic-design"]26compatibility: []27approvalRequired: "false"28approvalFor: []29metadata:30 source: https://skillmd.com/skills/quantumquirkxyz/graphic-design-project-management31---3233## Contract3435- Input: project brief, stakeholder map, deliverable list, timeline constraints, and quality requirements.36- Output: graphic design project management artifact with project plan, iteration schedule, review gates, and handoff standards.37- Scope: stay within the skill's declared boundaries; do not broaden without explicit direction.38- Rule: documented standards override defaults; explicit project rules take precedence.39- Rule: if blocked by missing context or dependencies, surface the blocker before proceeding.4041## Provenance4243| Question | Answer |44|---|---|45| What is the source of truth? | The user's request, originating spec/issue, and the skill's declared outputs |46| What is in scope? | Work covered by the skill's acceptance criteria and completion rules |47| What is explicitly out of scope? | Files, behaviors, and decisions outside the skill's declared boundary |48| Who or what consumes this artifact afterward? | The next skill in the workflow or the user |49| What evidence proves it is done? | Completion criteria met, artifact saved, validation passed |50| What risk remains? | Subjective judgment calls, missing context, or external dependency failures515253## Artifact5455Emit `GraphicDesignProjectManagementArtifact` as both:56- JSON: `.agents/skills/platform/artifacts/graphic-design-project-management/{identifier}.json`57- Markdown view: same filename with `.md` extension585960# 61# 62# Graphic Design Project Management6364Use this skill when a graphic design project needs explicit scope, timeline, iteration cycles, review gates, and asset handoff standards. It should translate stakeholder expectations into a durable project plan that keeps quality, feedback, and delivery visible.656667## Steps6869### 1. Define project scope and deliverables7071- List deliverables: posters, social graphics, brand assets, packaging, editorial layouts, presentations.72- Define acceptance criteria per deliverable: format, resolution, color space, brand compliance, accessibility.73- Define out-of-scope items explicitly.74- Identify dependencies between deliverables.7576**Completion criterion:** scope and deliverables with acceptance criteria saved.7778### 2. Plan timeline and milestones7980- Define project phases: discovery, concept, refinement, production, delivery.81- Assign estimated durations and milestone dates.82- Identify critical path and buffer time.83- Define dependencies between phases and deliverables.8485**Completion criterion:** timeline with milestones and critical path saved.8687### 3. Design iteration cycles8889- Define iteration structure: number of rounds, feedback format, revision limits.90- Separate internal review from stakeholder review.91- Define feedback window and response time expectations.92- Specify what constitutes a new iteration versus a minor revision.9394**Completion criterion:** iteration schedule with feedback rules saved.9596### 4. Define review gates and approval workflow9798- Define review stages: internal creative review, stakeholder review, brand review, legal review, final approval.99- Assign owner and approver per gate.100- Define approval criteria per gate.101- Define escalation path for blocked approvals.102103**Completion criterion:** review gates with owners, approvers, and criteria saved.104105### 5. Specify asset handoff standards106107- Define required formats per deliverable: source files, exported files, preview files.108- Define naming conventions: project code, deliverable type, version, date.109- Define folder structure and asset organization.110- Define versioning strategy: semantic versioning or date-based versioning.111- Define documentation requirements: readme, font licenses, color values, production notes.112113**Completion criterion:** asset handoff standards saved.114115### 6. Document quality gates116117- Define quality checks per deliverable: brand compliance, accessibility, resolution, color accuracy, spelling.118- Define who performs each check.119- Define pass/fail criteria.120- Define rework process for failed quality gates.121122**Completion criterion:** quality gate checklist with owners and criteria saved.123124### 7. Plan stakeholder communication125126- Define meeting cadence: standup, review, retro.127- Define communication channels: async updates, synchronous reviews.128- Define escalation path for blockers.129- Define retrospective schedule and format.130131**Completion criterion:** stakeholder communication plan saved.132133## Completion134135- the skill's completion criteria are explicitly checked136- the artifact is saved and validated137- any blockers or skipped validations are documented138- the next consumer is identified or the work is handed off139---140@include .agents/skills/platform/contract-base.xml