
Workflow
- 2 installs
- 627 repo stars
- Updated May 20, 2026
- waynesutton/markdown-site
Runs a project workflow for PRDs, task tracking, changelog sync, and documentation updates on multi-step or architecture-changing tasks.
About
This skill manages project workflow for non-trivial tasks, syncing PRDs, task tracking, changelog, and docs. A developer uses it for multi-step work spanning several files or architecture changes, and with @update to sync task, changelog, and files docs.
- Triage-first: identify, theorize, narrow, then act
- @update syncs task.md, changelog.md, and files.md
Workflow by the numbers
- 2 all-time installs (skills.sh)
- +1 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #2,419 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/waynesutton/markdown-site --skill workflowAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 2 |
|---|---|
| repo stars | ★ 627 |
| Last updated | May 20, 2026 |
| Repository | waynesutton/markdown-site ↗ |
What it does
Runs a project workflow for PRDs, task tracking, changelog sync, and documentation updates on multi-step or architecture-changing tasks.
Files
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 UTCLast Updated: YYYY-MM-DD HH:mm UTCStatus: 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.mdchangelog.mdfiles.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.