npx skills add https://github.com/davidk-cmyk/dk-replit-powerhouse --skill pm始终保持项目的问题跟踪器准确、优先级明确且可操作。代码库中的每次变更都应有对应的问题,每个问题都应反映当前实际情况。
# [ISSUE-XXX]: [简短的祈使句标题]
## Type
Bug | Feature | Task | Spike | Chore
## Status
Open | In Progress | In Review | Blocked | Done | Deferred | Canceled
## Priority
P0 (Critical) | P1 (High) | P2 (Medium) | P3 (Low)
## Description
这个问题的核心是什么?最多一段话。
## Acceptance Criteria
- [ ] AC-1: [可测试的结果]
- [ ] AC-2: ...
## Linked Artifacts
- Spec: [链接或文件路径]
- Plan Task: TASK-XXX
- PR/Commit: [引用]
- Blocking/Blocked by: ISSUE-YYY
## Notes / Context
任何额外的上下文、截图、复现步骤或讨论。
## History
| Date | Author | Action |
|------|--------|--------|
| YYYY-MM-DD | [Name] | Created |
| YYYY-MM-DD | [Name] | Status → In Progress |
| 类型 | 何时使用 | 示例 |
|---|
Keep the project's issue tracker accurate, prioritized, and actionable at all times. Every change in the codebase should have a corresponding issue, and every issue should reflect the current state of reality.
# [ISSUE-XXX]: [Short imperative title]
## Type
Bug | Feature | Task | Spike | Chore
## Status
Open | In Progress | In Review | Blocked | Done | Deferred | Canceled
## Priority
P0 (Critical) | P1 (High) | P2 (Medium) | P3 (Low)
## Description
What is this issue about? One paragraph max.
## Acceptance Criteria
- [ ] AC-1: [Testable outcome]
- [ ] AC-2: ...
## Linked Artifacts
- Spec: [link or file path]
- Plan Task: TASK-XXX
- PR/Commit: [reference]
- Blocking/Blocked by: ISSUE-YYY
## Notes / Context
Any additional context, screenshots, reproduction steps, or discussion.
## History
| Date | Author | Action |
|------|--------|--------|
| YYYY-MM-DD | [Name] | Created |
| YYYY-MM-DD | [Name] | Status → In Progress |
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
| Bug | 某些功能损坏或行为不正确 | "邮箱包含加号时登录返回 500 错误" |
| Feature | 面向用户的新功能 | "添加密码重置流程" |
| Task | 用户不可见的工程工作 | "设置 CI 流水线" |
| Spike | 限时研究以降低不确定性 | "评估支付服务提供商(最多 2 小时)" |
| Chore | 维护、升级、清理工作 | "升级 Node.js 到 v20" |
| 优先级 | 含义 | 响应时间 |
|---|---|---|
| P0 — 严重 | 系统宕机、数据丢失、安全漏洞 | 放下一切;立即修复 |
| P1 — 高 | 主要功能损坏,阻塞其他工作 | 在当前冲刺周期内修复 |
| P2 — 中 | 重要但不紧急;存在变通方案 | 安排在下个冲刺周期 |
| P3 — 低 | 锦上添花、小优化、技术债务 | 待办列表;有容量时处理 |
当新问题进入时:
将待办列表作为 Markdown 文件存储在代码库中:
/docs/
backlog.md ← 主问题列表
issues/
ISSUE-001.md ← 单个问题文件(针对复杂问题)
ISSUE-002.md
对于小型项目,一个包含表格的单一 backlog.md 文件即可:
| ID | Type | Priority | Title | Status | Owner | Updated |
|----|------|----------|-------|--------|-------|---------|
| 001 | Bug | P1 | Login fails with + in email | In Progress | @dev | 2025-01-15 |
| 002 | Feature | P2 | Add password reset | Open | — | 2025-01-14 |
# Status Update: [Date]
## Summary
一句话概括:自上次更新以来发生了什么。
## Completed
- [ISSUE-XXX] [Title] — Done
- [ISSUE-YYY] [Title] — Done
## In Progress
- [ISSUE-ZZZ] [Title] — [% complete or current step]
## Blocked
- [ISSUE-AAA] [Title] — Blocked by: [reason]. Unblock path: [action].
## Up Next
- [ISSUE-BBB] [Title] — Starting [when]
## Risks / Flags
- [Any new risks, scope changes, or timeline concerns]
PM 技能是整个工作流程的连接纽带:
| 工作流程步骤 | PM 操作 |
|---|---|
| spec | 为规格说明中的每个主要功能创建 Feature 问题 |
| plan | 将 TASK-XXX 条目链接到相应的问题;更新估算 |
| tdd | 当测试揭示意外行为时,记录 Bug 问题 |
| build | 随着工作进展,将问题状态更新为 In Progress / In Review |
| code-review | 为未立即修复的审查发现创建新问题 |
| test | 为测试失败创建 Bug 问题;测试通过时更新状态 |
| tech-writer | 为文档审查期间发现的文档缺口创建 Chore 问题 |
backlog.md 存储在 /docs/ 目录下,以便在 Replit 文件树中与规格说明和计划一起可见。backlog.md 以选择下一个问题。fix: resolve ISSUE-012 login error。每周安装次数
1
仓库
首次出现
1 天前
安全审计
安装于
replit1
amp1
cline1
opencode1
cursor1
kimi-cli1
| Type | When to Use | Example |
|---|---|---|
| Bug | Something is broken or behaving incorrectly | "Login returns 500 when email has a plus sign" |
| Feature | New user-facing functionality | "Add password reset flow" |
| Task | Engineering work that isn't user-visible | "Set up CI pipeline" |
| Spike | Time-boxed research to reduce uncertainty | "Evaluate payment providers (2hr max)" |
| Chore | Maintenance, upgrades, cleanup | "Upgrade Node.js to v20" |
| Priority | Meaning | Response Time |
|---|---|---|
| P0 — Critical | System down, data loss, security breach | Drop everything; fix now |
| P1 — High | Major feature broken, blocking other work | Fix within current sprint |
| P2 — Medium | Important but not urgent; workaround exists | Schedule in next sprint |
| P3 — Low | Nice to have, minor polish, tech debt | Backlog; do when capacity allows |
When new issues come in:
Store the backlog as a Markdown file in the repo:
/docs/
backlog.md ← master issue list
issues/
ISSUE-001.md ← individual issue files (for complex issues)
ISSUE-002.md
For small projects, a single backlog.md with a table is sufficient:
| ID | Type | Priority | Title | Status | Owner | Updated |
|----|------|----------|-------|--------|-------|---------|
| 001 | Bug | P1 | Login fails with + in email | In Progress | @dev | 2025-01-15 |
| 002 | Feature | P2 | Add password reset | Open | — | 2025-01-14 |
# Status Update: [Date]
## Summary
One sentence: what happened since last update.
## Completed
- [ISSUE-XXX] [Title] — Done
- [ISSUE-YYY] [Title] — Done
## In Progress
- [ISSUE-ZZZ] [Title] — [% complete or current step]
## Blocked
- [ISSUE-AAA] [Title] — Blocked by: [reason]. Unblock path: [action].
## Up Next
- [ISSUE-BBB] [Title] — Starting [when]
## Risks / Flags
- [Any new risks, scope changes, or timeline concerns]
The PM skill is the connective tissue across the entire workflow:
| Workflow Step | PM Action |
|---|---|
| spec | Create Feature issues for each major capability in the spec |
| plan | Link TASK-XXX entries to corresponding issues; update estimates |
| tdd | Log Bug issues when tests reveal unexpected behavior |
| build | Move issues to In Progress / In Review as work progresses |
| code-review | Create new issues for review findings that aren't fixed immediately |
| test | Create Bug issues for test failures; update status when tests pass |
| tech-writer | Create Chore issues for documentation gaps discovered during docs review |
backlog.md in /docs/ so it's visible in the Replit file tree alongside specs and plans.backlog.md to pick the next issue.fix: resolve ISSUE-012 login error.Weekly Installs
1
Repository
First Seen
1 day ago
Security Audits
Installed on
replit1
amp1
cline1
opencode1
cursor1
kimi-cli1
站立会议模板:敏捷开发每日站会指南与工具(含远程团队异步模板)
10,500 周安装