Skip to content
cccskills
FreePublished on GitHub

workflow

Project workflow for PRDs, task tracking, changelog sync, and documentation updates. Use for any non-trivial task that spans multiple steps, touches several files, changes architecture, or needs project tracking updates. Also activates with @update to sync task.md, changelog.md, and files.md after completing work.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md2.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Project Workflow Skill

Use this skill for any non trivial task that spans multiple steps, touches several files, changes architecture, or needs project tracking updates.

Activate with: @update (for docs sync only)

Triage first

Before changing code:

  1. Identify what is missing, broken, or incomplete.
  2. Theorize a few likely causes or approaches.
  3. Narrow to the most likely plan.
  4. Ask if anything important is still unclear.

Skip the long process only for obvious one file fixes like typos or tiny copy changes.

PRD rules

Create a PRD before non trivial work.

  • Path: prds/<feature-or-problem-slug>.md
  • Extension: .md
  • Include:
    • problem
    • root cause for bugs
    • proposed solution
    • files to change
    • edge cases
    • verification steps
    • task completion log

Add metadata at the top:

  • Created: YYYY-MM-DD HH:mm UTC
  • Last Updated: YYYY-MM-DD HH:mm UTC
  • Status: Draft | In Progress | Done

Task tracking

Update task.md as the work moves forward.

  • Put new work under ## to do
  • Move finished work to ## completed
  • Add timestamps in YYYY-MM-DD HH:mm UTC
  • Do not mark a task done until it has been verified
  • Keep task notes short but specific enough for the next session

When useful, include:

  • the PRD path
  • the files touched
  • the verification command or outcome

Docs sync after changes

After each feature or fix, sync the project docs:

  • task.md
  • changelog.md
  • files.md

For changelog.md:

  • use Keep a Changelog structure
  • get real dates from git log --date=short -n 10
  • add timestamps when helpful

For files.md:

  • add new files
  • update descriptions that changed
  • keep descriptions brief and concrete

Execution style

  • Use subagents for research or parallel analysis when the task is large enough to benefit.
  • Use one focused subagent per task.
  • Stop and re plan if the work stops making sense.
  • Keep the change set tight.
  • Ask whether a staff engineer would approve the result before calling it done.

Learning loop

If the user corrects a repeated pattern, record the lesson in prds/lessons.md so the mistake does not come back.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

adapt

Free

Adapt designs to work across different screen sizes, devices, contexts, or platforms. Implements breakpoints, fluid layouts, and touch targets. Use when the user mentions responsive design, mobile layouts, breakpoints, viewport adaptation, or cross-device compatibility.

The English summary is being prepared. Showing the original description.

waynesutton/waynesutton-ai2Updated Sep 8, 2026

Agent Ready project design context for navigation, docs links, and interface tone. Use when building or reviewing UI in this repo so patterns match the documented product feel.

The English summary is being prepared. Showing the original description.

waynesutton/waynesutton-ai2Updated Sep 8, 2026

Review a feature and enhance it with purposeful animations, micro-interactions, and motion effects that improve usability and delight. Use when the user mentions adding animation, transitions, micro-interactions, motion design, hover effects, or making the UI feel more alive.

The English summary is being prepared. Showing the original description.

waynesutton/waynesutton-ai2Updated Sep 8, 2026

Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition.

The English summary is being prepared. Showing the original description.

waynesutton/waynesutton-ai2Updated Sep 8, 2026

audit

Free

Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.

The English summary is being prepared. Showing the original description.

waynesutton/waynesutton-ai2Updated Sep 8, 2026

Layout structure for web interfaces, from grouping and alignment to reading order, progressive disclosure, and adaptive breakpoints. Use when structuring a page or component, spacing or aligning controls, deciding what collapses at small sizes, handling RTL layout direction, or reviewing frontend code for layout. Triggers on layout, spacing, alignment, grouping, negative space, whitespace, visual hierarchy, reading order, progressive disclosure, breakpoints, responsive layout, container queries, safe area, full-bleed, edge-to-edge, layout margins, RTL layout, logical properties.

The English summary is being prepared. Showing the original description.

waynesutton/waynesutton-ai2Updated Sep 8, 2026

See all skills by waynesutton

Report a problem with this skill