Run any Skill in Manus with one click

planning-workflow

Stars0

Forks0

UpdatedJune 11, 2026 at 09:55

Prioritization framework, sprint sequencing, and success criteria for uFawkes.dev work. Used by Planning agent to sequence issues across PRs and agents.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

paruff

paruff/uFawkes.dev

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Project Management SpecialistsBusiness and Financial Operations Occupations·SOC 13-1082

SKILL.md

readonly

name	planning-workflow
description	Prioritization framework, sprint sequencing, and success criteria for uFawkes.dev work. Used by Planning agent to sequence issues across PRs and agents.
license	MIT
compatibility	opencode

Planning Workflow

Prioritization framework

P0 — Broken (fix immediately, before any other work)

Trust-damaging content that is live on the site right now. Examples: zero-star badges, "Screenshot placeholder" text, raw Liquid rendering as text.

P1 — Conversion (fix this sprint)

Blocks the primary visitor action. A Builder or Operator cannot complete their journey. Examples: no CTA above fold, buried quick start, broken cross-links.

P2 — Quality (fix next sprint)

Weakens credibility or comprehension. Visitor can still act but leaves with less confidence. Examples: generic meta descriptions, stub content, repeated "coming soon" notices.

P3 — Polish (deferred)

Minor improvements. No visitor impact, just cleaner. Examples: section label tweaks, formatting consistency.

Sprint structure

Sprint 1 — PR 1 (all P0 and P1 issues in index.md) Sequence: #1 → #3 → #4 → #9 → #2 → #10 → #5 → #11 → #12

Rationale: fix trust-damaging first (#1 double H1, #3 fake badges, #4 bad alt text), then consolidate notices (#9), then conversion (#2 CTA reorder, #10 hero CTA), then polish (#5 Dojo callout, #11 label, #12 DORA descriptions).

Sprint 2 — PR 2 (stack pages and learn guides) Sequence: #6 (all 5 stack pages) → #8 (all 5 meta descriptions) → #7 (learn guides + guide-meta include)

Sprint 3 — PR 3 (design system — deferred) Do not start until PR 1 and PR 2 are merged and live.

Sprint 4 — PR 4 (agent/skill infrastructure) Can run in parallel with Sprint 2. No site file conflicts.

Success criteria per issue

An issue is ✅ Done when:

Build passes (make build exits 0)
Review agent has approved
Commit is on main (merged)
Planning agent has updated Section 8 status
Live site reflects the change (within GitHub Pages deploy time, ~2 min)

AGENTS.md update checklist

After each issue completes:

Change ⬜ Not started → ✅ Done in Section 8
Update Section 12 handoff block
Commit: docs(agents): mark issue #N complete

After each PR merges:

Verify all issues in the PR are marked ✅
Update Section 12 to show next sprint starting

More from this repository

same repository

code-quality

paruff/uFawkes.dev

Code quality standards for uFawkes.dev — Jekyll/Liquid linting rules, CSS validation, HTML structure checks, and review thresholds. Used by Review and Build agents.

2026-06-110

component-workflow

paruff/uFawkes.dev

Full lifecycle for uFawkes components — anatomy definition, implementation spec, styling rules, and Jekyll/Liquid integration patterns. For UI and Build agents.

2026-06-110

cross-agent-coordination

paruff/uFawkes.dev

Handoff protocol, dependency sequencing, and parallel task rules for the uFawkes agent team. Ensures agents don't conflict, block each other, or duplicate work.

2026-06-110

accessibility-workflow

paruff/uFawkes.dev

Three-phase accessibility workflow for uFawkes.dev — audit (find issues), remediate (fix specifications), verify (confirm compliance). Covers WCAG AA, Jekyll/HTML patterns, and vanilla CSS focus states.

2026-06-090

content-strategy

paruff/uFawkes.dev

Content strategy for uFawkes.dev — narrative structure, page-level content hierarchy, tone guidelines, CTA copy patterns, and trust signal rules.

2026-06-090

design-system-workflow

paruff/uFawkes.dev

Process for evolving the Fawkes Design System (FDS) — token definition, pattern library maintenance, compliance checking, and documentation. Currently in bootstrap phase.

2026-06-090

name	planning-workflow
description	Prioritization framework, sprint sequencing, and success criteria for uFawkes.dev work. Used by Planning agent to sequence issues across PRs and agents.
license	MIT
compatibility	opencode

Planning Workflow

Prioritization framework

P0 — Broken (fix immediately, before any other work)

Trust-damaging content that is live on the site right now. Examples: zero-star badges, "Screenshot placeholder" text, raw Liquid rendering as text.

P1 — Conversion (fix this sprint)

Blocks the primary visitor action. A Builder or Operator cannot complete their journey. Examples: no CTA above fold, buried quick start, broken cross-links.

P2 — Quality (fix next sprint)

Weakens credibility or comprehension. Visitor can still act but leaves with less confidence. Examples: generic meta descriptions, stub content, repeated "coming soon" notices.

P3 — Polish (deferred)

Minor improvements. No visitor impact, just cleaner. Examples: section label tweaks, formatting consistency.

Sprint structure

Sprint 1 — PR 1 (all P0 and P1 issues in index.md) Sequence: #1 → #3 → #4 → #9 → #2 → #10 → #5 → #11 → #12

Sprint 2 — PR 2 (stack pages and learn guides) Sequence: #6 (all 5 stack pages) → #8 (all 5 meta descriptions) → #7 (learn guides + guide-meta include)

Sprint 3 — PR 3 (design system — deferred) Do not start until PR 1 and PR 2 are merged and live.

Sprint 4 — PR 4 (agent/skill infrastructure) Can run in parallel with Sprint 2. No site file conflicts.

Success criteria per issue

An issue is ✅ Done when:

Build passes (make build exits 0)
Review agent has approved
Commit is on main (merged)
Planning agent has updated Section 8 status
Live site reflects the change (within GitHub Pages deploy time, ~2 min)

AGENTS.md update checklist

After each issue completes:

Change ⬜ Not started → ✅ Done in Section 8
Update Section 12 handoff block
Commit: docs(agents): mark issue #N complete

After each PR merges:

Verify all issues in the PR are marked ✅
Update Section 12 to show next sprint starting