个人作者
Серёжа
Хроникёр рынка. Product Owner в Skillaz, B2B/B2C, HRTech, Edtech, IT. Здесь коротко про продукт, найм, AI.
- Skills
- 23
- 仓库
- 1
- 职业覆盖
- 3
- 场景覆盖
- 3
- Stars
- ★ 16
Серёжа 的 Skills 23
bad
暂无简介
writing-skills
Use when creating, editing, or validating reusable agent skills and their trigger behavior. Do NOT use for ordinary project documentation or one-off prompts.
writing-plans
Use when an approved change spans multiple dependent outcomes and needs a durable implementation sequence before coding. Do NOT use for small, obvious, reversible edits.
verification-before-completion
Use when about to claim work is complete, fixed, passing, or ready to integrate. Do NOT use to repeat checks without a completion claim or concrete doubt.
using-superpowers
Use when starting a conversation or deciding whether a Superpowers workflow matches the current task. Do NOT use it to auto-invoke skills whose stated triggers do not match.
using-git-worktrees
Use when feature work needs isolation from the current workspace or before executing a risky implementation plan. Do NOT use when the current workspace is already safe and isolated.
test-driven-development
Use when implementing a high-risk behavior change, reproduced regression, or costly contract. Do NOT use by default for docs, styling, config, or low-risk wiring.
systematic-debugging
Use when diagnosing a bug, failing check, unexpected behavior, or production incident before changing code. Do NOT use for known mechanical edits without a failure.
subagent-driven-development
Use when the user requests delegated implementation or multiple substantial tasks are genuinely independent without shared state. Do NOT use for coupled or ordinary single-task work.
requesting-code-review
Use when a completed change is high-risk, crosses subsystem boundaries, or the user explicitly requests independent review. Do NOT use by default for low- or medium-risk changes.
receiving-code-review
Use when receiving code review feedback that may be unclear or technically questionable and needs verification. Do NOT use for an unrequested general code review.
finishing-a-development-branch
Use when verified implementation is ready and the user must choose whether to keep, merge, or publish the branch. Do NOT use before applicable checks pass.
executing-plans
Use when implementing an approved written plan with dependent tasks in the current session. Do NOT use when the plan is missing, unapproved, or naturally parallel.
dispatching-parallel-agents
Use when 2 or more substantial tasks are independent, have disjoint state, and parallel execution will save meaningful time. Do NOT use for coupled or sequential work.
brainstorming
Use when a request leaves material product, architecture, behavior, or scope decisions unresolved. Do NOT use for approved, well-bounded implementation work.
tg-post-writer
Use when the user asks "напиши пост в тг / оформи это для телеграма / сделай tg-пост про X". Target: personal channel or group Telegram posts in Russian, in the channel's established voice. SKIP: posts for other platforms (Twitter, LinkedIn, Habr — use separate skills), formal press releases.
spec
Short alias for the global product-spec-pipeline skill. Use when the user invokes `$spec` to turn a product idea, feature, improvement, or small task into a researched and independently reviewed product specification. Trigger: `$spec` followed by the idea or task. Do NOT use for technical architecture, implementation plans, or API documentation.
ru-pr-description
Use when the user asks "напиши PR / сгенерь PR description / опиши что я делал в этой ветке". Also trigger automatically before `gh pr create` when no `--body` argument was provided. SKIP: if the PR already has a description, or for draft PRs explicitly marked "wip".