AgentSkillsCN

project-ops

对项目每日站会的会议记录进行处理，生成会议摘要，并更新任务矩阵、README、CHANGELOG以及会议索引。适用于日常站会、冲刺回顾，或在带有冲刺追踪的活跃项目中召开团队会议。

SKILL.md
--- frontmatter
name: project-ops
description: Process project standup transcripts with full status updates. Creates meeting summary and updates task matrix, README, CHANGELOG, and meetings index. Use for daily standups, sprint reviews, or team meetings on active projects with sprint tracking.
user-invocable: true
argument-hint: [standup transcript or meeting content]

Project Operations Framework

Process project standup transcripts into comprehensive documentation with full status tracking.

Base framework: Extends ops-base -- read ~/.claude/skills/ops-base/SKILL.md for shared standards (meeting formats, task management, workflows, archive policy).

IMPORTANT: The project CLAUDE.md is the single source of truth for project-specific details. This skill defines the processing workflow; CLAUDE.md defines file locations and naming conventions.

5-FILE UPDATE WORKFLOW

When processing a standup transcript, update ALL of these files:

1. Meeting Summary

Location: Consult CLAUDE.md MEETING ROUTING, default: meetings/YYMMDD-participants-daily-standup.md

Structure (8+ numbered sections):

markdown
# Daily Standup - [Month Day, Year]

**Date**: YYYY-MM-DD
**Time**: HH:MM
**Participants**: [Names with roles]
**Format**: [Video call / In-person]

---

[2-3 sentence executive summary]

---

## 1. Completed

| Item | Owner | Notes |
|------|-------|-------|
| [Work item] | [Name] | [Context] |

## 2. In Progress

| Item | Owner | Status |
|------|-------|--------|
| [Work item] | [Name] | [Status note] |

## 3. Key Technical Updates

### [Topic Name]
- **Before**: [Previous state]
- **Now**: [Current state]
- **Result**: [Impact]

## 4. Issues Discovered

### [Issue Title]
- **Reported by**: [Name]
- **Symptom**: [What happens]
- **Severity**: HIGH/MEDIUM/LOW
- **Status**: [Investigation/Resolved/In Progress]

## 5. Decisions Made

| Decision | Rationale |
|----------|-----------|
| [Decision] | [Why] |

## 6. Action Items

| Action | Owner | Priority | Due |
|--------|-------|----------|-----|
| [Action] | [Name] | P0/P1/P2/P3 | [When] |

## 7. Version Status (if applicable)

| Version | Platform | Status | Notes |
|---------|----------|--------|-------|
| [Version] | [Platform] | [Status] | [Notes] |

## 8. Status Summary

| Component | Status | Notes |
|-----------|--------|-------|
| [Feature] | [FIXED/WORKING/ISSUE/PARTIAL] | [Notes] |

---

**Next Standup**: [Date]
**Focus**: [Main topics]
**Key Blocker**: [If any]

2. task-priority-matrix.md

Location: Project root

Updates:

  • •Last Updated date
  • •Timeline Note section with current status
  • •Current Sprint Focus table
  • •Individual team member task tables
  • •Move completed items to Completed This Week
  • •Add new tasks discovered
  • •Update Known Issues section

3. README.md

Location: Project root

Updates:

  • •Current Status section with date and summary
  • •Component status table
  • •Active Tasks table with current focus
  • •Recent Meetings table (add new entry at top)
  • •Testing Summary if applicable
  • •Last Updated date at bottom

4. CHANGELOG.md

Location: Project root

Add entry at top:

markdown
## [YYYY-MM-DD]

### Added
- Created daily standup summary: `meetings/YYMMDD-participants-daily-standup.md`
  - [Key points from meeting]

### Changed
- Updated `README.md` - [Date] status update
  - [Key changes]
- Updated `task-priority-matrix.md` - [Date] priorities
  - [Key changes]

### Development Status (v[Version])
- **[Feature]**: [STATUS] - [Notes]

5. meetings/README.md (or meetings index)

Location: meetings/README.md

Updates:

  • •Add new entry to Recent Meetings Index table

STATUS TERMINOLOGY

Work Status

  • •VERIFIED - Tested and confirmed working
  • •DISPLAYED - UI visible but functionality not tested
  • •NOT_TESTED - Not covered yet
  • •ISSUE - Tested and broken
  • •PARTIAL - Partially working/tested

Resolution Status

  • •FIXED - Issue resolved
  • •IMPROVED - Better but not complete
  • •WORKING - Functioning correctly
  • •BLOCKED - External dependency
  • •DEFERRED - Postponed deliberately

Priority Levels

  • •P0 - Critical blocker, immediate action
  • •P1 - High priority, this week
  • •P2 - Important, within 2 weeks
  • •P3 - Research/exploration, flexible

ISSUE ID FORMAT

Format: [SEVERITY]-[YYMMDD]-[###]

Severity codes:

  • •CRIT - P0 Critical (release blocker)
  • •HIGH - P1 High priority
  • •MED - P2 Medium priority
  • •LOW - P3 Low priority

Example: CRIT-260212-001

PROCESSING INSTRUCTIONS

Step 1: Parse Transcript

Extract from the transcript:

  • •Participants and their roles
  • •Completed work items (who did what)
  • •In-progress work (current status)
  • •Technical updates and decisions
  • •Issues/blockers discovered
  • •Action items with owners and deadlines
  • •Version/build information if mentioned

Step 2: Create Meeting Summary

  1. •Determine date from transcript or filename
  2. •Follow the 8-section structure above
  3. •Use tables for structured data
  4. •Include technical detail where relevant
  5. •Attribute actions to correct people

Step 3: Update task-priority-matrix.md

  1. •Read current file
  2. •Update Last Updated date
  3. •Update Timeline Note with current status
  4. •Move completed items to Completed This Week
  5. •Update task statuses in team member sections
  6. •Add new tasks discovered in meeting
  7. •Update Known Issues section

Step 4: Update README.md

  1. •Read current file
  2. •Update Current Status section with date and summary
  3. •Update component status table
  4. •Update Active Tasks table
  5. •Add new entry to Recent Meetings table
  6. •Update Testing Summary if applicable
  7. •Update Last Updated date

Step 5: Update CHANGELOG.md

  1. •Read current file
  2. •Add new entry at top following format
  3. •Include development status section
  4. •Reference the meeting summary file

Step 6: Update meetings/README.md

  1. •Read current file
  2. •Add new entry to Recent Meetings Index table

OUTPUT REQUIREMENTS

Language

Maintain the same language as the transcript unless project CLAUDE.md specifies otherwise.

Accuracy

  • •Verify participant attribution before finalizing
  • •Cross-check numbers, dates, and technical specs
  • •Ensure all decisions are captured with rationale

Cross-References

  • •Link to meeting summary from CHANGELOG
  • •Link to related documents where relevant
  • •Use relative paths for all links

File Naming

Follow project CLAUDE.md conventions. Defaults:

  • •Meetings: YYMMDD-participants-daily-standup.md
  • •Use lowercase with hyphens
  • •Only CHANGELOG.md and README.md are uppercase

FALLBACK BEHAVIOR

If no CLAUDE.md exists:

  • •Use default file locations listed above
  • •Use default naming conventions
  • •Create files if they don't exist
  • •Ask user for confirmation on file locations

If a file doesn't exist:

  • •For README.md: Create basic structure
  • •For CHANGELOG.md: Create with initial entry
  • •For task-priority-matrix.md: Ask user before creating
  • •For meetings/README.md: Create basic index