How do I install the Personal Weekly Workflow skill?

Run npx skillmds add majiayu000/personal-weekly-workflow in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Personal Weekly Workflow safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Personal Weekly Workflow?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Personal Weekly Workflow free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Personal Weekly Workflow?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Personal Weekly Workflow by majiayu000

Name: Personal Weekly Workflow
Rating: 4.666666666666667 (3 reviews)
Author: majiayu000

Personal Weekly Workflow

Manage weekly PM workflows, meeting notes, and action items for the Orient Task Force. Use this skill when asked about "weekly planning", "meeting notes", "action items", "sprint health", "weekly summary", or workflow automation. Covers Monday planning, Wednesday health checks, Friday summaries, meeting note templates, action item format, and JIRA synchronization.

majiayu000 df43906 2 files · 5.0 KB Updated Sep 9, 2026 567 repo stars

File contents

Workflow Management for Orient PM

Directory Structure

meetings/              # Meeting notes
├── weekly/           # Weekly team meetings
├── planning/         # Sprint planning
├── retrospectives/   # Sprint retrospectives
├── 1-on-1/          # One-on-one meetings
├── ad-hoc/          # Ad-hoc meetings
└── templates/       # Meeting templates

workflow/             # Weekly workflow
├── weekly-reviews/  # Weekly planning docs
├── sprint-health/   # Mid-sprint health checks
└── weekly-summaries/# End-of-week summaries

Weekly Rhythm

Monday - Start Week

npm run workflow:start-week

Fetches current JIRA state
Lists blockers and in-progress items
Creates planning doc

Wednesday - Mid-Sprint Check

npm run workflow:mid-sprint

Calculates burndown
Identifies at-risk items
Updates health status

Friday - End Week

npm run workflow:end-week
npm run update-presentation

Lists completed work
Calculates velocity
Updates rolling presentation

Meeting Notes

Create Meeting Note

npm run meeting:new [type] "[title]"

Types: weekly, planning, retrospective, 1-on-1, ad-hoc

Action Item Format

- [ ] @username: Description [Task] [Priority: High] #YOUR_PROJECT-123

Components:

[ ] = Open, [x] = Completed
@username = Assignee (match JIRA user)
[Task] / [Story] / [Bug] = Issue type
[Priority: High] = Priority level
#YOUR_PROJECT-XXX = Existing JIRA issue (optional)

Sync Action Items to JIRA

npm run meeting:sync <file>

List All Action Items

npm run meeting:list
npm run meeting:report

CLI Commands Quick Reference

# Meetings
npm run meeting:new [type] "[title]"    # Create meeting note
npm run meeting:sync <file>              # Sync action items to JIRA
npm run meeting:list                     # List all action items
npm run meeting:report                   # Generate report

# Workflow
npm run workflow:start-week              # Monday planning
npm run workflow:mid-sprint              # Wednesday check
npm run workflow:end-week                # Friday summary

# Presentation
npm run update-presentation              # Update rolling deck

Day-Specific Suggestions

Monday Morning

Create weekly planning doc
Review last week's summary
Check for blockers and SLA breaches
List open action items from meetings

Wednesday

Generate sprint health check
Show current blockers
Check SLA breaches

Friday Afternoon

Generate weekly summary
Update rolling presentation
Create action items report
Preview next week's priorities

Finding Action Items

Find all open action items:

Search: "- [ ]" in meetings/

Find your action items:

Search: "@yourusername" and "- [ ]"

Find high priority items:

Search: "[Priority: High]" and "- [ ]"

Find unlinked items (no JIRA):

Search: "- [ ]" NOT "#YOUR_PROJECT"

Meeting → JIRA Flow

During meeting: Take notes in meeting template
Action items: Add with format above
Post-meeting: npm run meeting:sync <file>
Result: JIRA issues created, meeting updated with keys

Context Awareness

By Day

Monday: Focus on planning
Tuesday-Thursday: Execution, track blockers
Friday: Summary and wrap-up

By Sprint Phase

Sprint start: Planning mode
Mid-sprint: Execution, health checks
Sprint end: Retrospective, summary mode

By Role

PM: Metrics, reporting, stakeholder updates
Team member: Action items, blockers
Stakeholder: Summaries, high-level status

---name: personal-weekly-workflowdescription: Manage weekly PM workflows, meeting notes, and action items for the Orient Task Force. Use this skill when asked about "weekly planning", "meeting notes", "action items", "sprint health", "weekly summary", or workflow automation. Covers Monday planning, Wednesday health checks, Friday summaries, meeting note templates, action item format, and JIRA synchronization.--- # Workflow Management for Orient PM ## Directory Structure ``` meetings/ # Meeting notes ├── weekly/ # Weekly team meetings ├── planning/ # Sprint planning ├── retrospectives/ # Sprint retrospectives ├── 1-on-1/ # One-on-one meetings ├── ad-hoc/ # Ad-hoc meetings └── templates/ # Meeting templates workflow/ # Weekly workflow ├── weekly-reviews/ # Weekly planning docs ├── sprint-health/ # Mid-sprint health checks └── weekly-summaries/# End-of-week summaries ``` ## Weekly Rhythm ### Monday - Start Week ```bash npm run workflow:start-week ``` - Fetches current JIRA state - Lists blockers and in-progress items - Creates planning doc ### Wednesday - Mid-Sprint Check ```bash npm run workflow:mid-sprint ``` - Calculates burndown - Identifies at-risk items - Updates health status ### Friday - End Week ```bash npm run workflow:end-week npm run update-presentation ``` - Lists completed work - Calculates velocity - Updates rolling presentation ## Meeting Notes ### Create Meeting Note ```bash npm run meeting:new [type] "[title]" ``` Types: `weekly`, `planning`, `retrospective`, `1-on-1`, `ad-hoc` ### Action Item Format ```markdown - [ ] @username: Description [Task] [Priority: High] #YOUR_PROJECT-123 ``` Components: - `[ ]` = Open, `[x]` = Completed - `@username` = Assignee (match JIRA user) - `[Task]` / `[Story]` / `[Bug]` = Issue type - `[Priority: High]` = Priority level - `#YOUR_PROJECT-XXX` = Existing JIRA issue (optional) ### Sync Action Items to JIRA ```bash npm run meeting:sync <file> ``` ### List All Action Items ```bash npm run meeting:list npm run meeting:report ``` ## CLI Commands Quick Reference ```bash # Meetings npm run meeting:new [type] "[title]" # Create meeting note npm run meeting:sync <file> # Sync action items to JIRA npm run meeting:list # List all action items npm run meeting:report # Generate report # Workflow npm run workflow:start-week # Monday planning npm run workflow:mid-sprint # Wednesday check npm run workflow:end-week # Friday summary # Presentation npm run update-presentation # Update rolling deck ``` ## Day-Specific Suggestions ### Monday Morning 1. Create weekly planning doc 2. Review last week's summary 3. Check for blockers and SLA breaches 4. List open action items from meetings ### Wednesday 1. Generate sprint health check 2. Show current blockers 3. Check SLA breaches ### Friday Afternoon 1. Generate weekly summary 2. Update rolling presentation 3. Create action items report 4. Preview next week's priorities ## Finding Action Items **Find all open action items:** ``` Search: "- [ ]" in meetings/ ``` **Find your action items:** ``` Search: "@yourusername" and "- [ ]" ``` **Find high priority items:** ``` Search: "[Priority: High]" and "- [ ]" ``` **Find unlinked items (no JIRA):** ``` Search: "- [ ]" NOT "#YOUR_PROJECT" ``` ## Meeting → JIRA Flow 1. **During meeting:** Take notes in meeting template 2. **Action items:** Add with format above 3. **Post-meeting:** `npm run meeting:sync <file>` 4. **Result:** JIRA issues created, meeting updated with keys ## Context Awareness ### By Day - Monday: Focus on planning - Tuesday-Thursday: Execution, track blockers - Friday: Summary and wrap-up ### By Sprint Phase - Sprint start: Planning mode - Mid-sprint: Execution, health checks - Sprint end: Retrospective, summary mode ### By Role - PM: Metrics, reporting, stakeholder updates - Team member: Action items, blockers - Stakeholder: Summaries, high-level status

Frequently asked questions