Menü
Use this skill when generating project updates, status reports, or stakeholder communications.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Use this skill when investigating blockers, stalled work, or anything preventing progress.
Use this skill when the user asks about deepagents harness capabilities, tool names, task delegation, filesystem access, or sandbox execution. It provides a concise operational cheat sheet.
Use this skill for multi-track tasks that benefit from delegation, parallel research, or structured planning. It guides the main agent to use the task tool, subagents, and write_todos for coordination.
Use this skill for requests related to Linear issues, projects, sprints, and team workload. This skill provides guidance on how to effectively query and interact with Linear data.
Use this skill for tasks that require running commands or scripts in the sandbox. It provides a plan-first workflow for using run_sandbox_workflow, dependency setup, verification, and iterative loops.
Guide for creating or updating skills. Covers naming, required frontmatter, store-backed paths, and publishing.
| name | project-status |
| description | Use this skill when generating project updates, status reports, or stakeholder communications. |
This skill helps generate project status updates and stakeholder communications.
Collect information from multiple sources:
get_linear_cycle_status - Sprint progressget_linear_project_status - Project healthget_linear_issues(filter: "blockers") - Current blockerssearch_memories(query: "decision shipped completed") - Recent winsExecutive format (for stakeholders):
## Summary
[1-2 sentences: what matters most]
## Progress
- Shipped: [what's done]
- In progress: [what's being worked on]
- Coming up: [what's next]
## Risks & Blockers
[Any issues that need attention]
## Key Decisions
[Recent decisions and their impact]
Team format (for standups):
## Sprint Status
[X]% complete | [Y] days remaining
## Blockers
[List with owners]
## Today's Focus
[Top priorities]
| Audience | Focus On | Avoid |
|---|---|---|
| Executives | Impact, timelines, risks | Technical details |
| Stakeholders | Features, dates, blockers | Implementation |
| Team | Blockers, priorities, help needed | High-level strategy |
| Customers | Value delivered, coming soon | Internal challenges |
Don't hide problems. Present them with:
## Sprint 23 Status
Progress: 65% complete (6 days remaining)
**Shipped:**
- User authentication (ABC-101)
- Dashboard redesign (ABC-102)
**In Progress:**
- API refactor (ABC-103) - 80% done
- Search feature (ABC-104) - blocked
**Needs Attention:**
- Search feature blocked on security review
- Escalating to security team today
**Coming Up:**
- Performance optimization
- Mobile responsiveness
**Key Decision:**
- Decided to use PostgreSQL for new data model
(Rationale: team expertise, query patterns)