원클릭으로 Manus에서 모든 스킬 실행

시작하기

project-status

스타3

포크0

업데이트2026년 2월 9일 23:12

Use this skill when generating project updates, status reports, or stakeholder communications.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

dkarasiewicz

dkarasiewicz/launchline

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Project Status Skill

Overview

This skill helps generate project status updates and stakeholder communications.

When to Use

"How's the sprint going?"
"Generate a project update"
"What should I tell stakeholders?"
"Give me a status summary"

Instructions

1. Gather Data

Collect information from multiple sources:

get_linear_cycle_status - Sprint progress
get_linear_project_status - Project health
get_linear_issues(filter: "blockers") - Current blockers
search_memories(query: "decision shipped completed") - Recent wins

2. Structure the Update

Executive 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]

3. Tailor to Audience

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

4. Be Honest About Risks

Don't hide problems. Present them with:

What the risk is
What's being done about it
What help is needed

Example Sprint Status

## 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)

이 저장소의 다른 Skills

같은 저장소

blocker-detection

dkarasiewicz/launchline

Use this skill when investigating blockers, stalled work, or anything preventing progress.

2026-02-093

deepagents-harness

dkarasiewicz/launchline

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.

2026-02-093

delegation-orchestration

dkarasiewicz/launchline

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.

2026-02-093

linear-integration

dkarasiewicz/launchline

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.

2026-02-093

sandbox-automation

dkarasiewicz/launchline

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.

2026-02-093

skill-creator

dkarasiewicz/launchline

Guide for creating or updating skills. Covers naming, required frontmatter, store-backed paths, and publishing.

2026-02-093

name	project-status
description	Use this skill when generating project updates, status reports, or stakeholder communications.

Project Status Skill

Overview

This skill helps generate project status updates and stakeholder communications.

When to Use

"How's the sprint going?"
"Generate a project update"
"What should I tell stakeholders?"
"Give me a status summary"

Instructions

1. Gather Data

Collect information from multiple sources:

get_linear_cycle_status - Sprint progress
get_linear_project_status - Project health
get_linear_issues(filter: "blockers") - Current blockers
search_memories(query: "decision shipped completed") - Recent wins

2. Structure the Update

Executive 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]

3. Tailor to Audience

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

4. Be Honest About Risks

Don't hide problems. Present them with:

What the risk is
What's being done about it
What help is needed

Example Sprint Status

## 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)