效率提升技能

Use when deciding whether a request needs an analiz task before implementation - the conditions that require the architect's analysis versus going straight to implementation

中文简介正在准备中。当前显示原文说明。

Use when a stakeholder sends a request - route it to backlog tasks, an analiz task, or a focused question, decide ask-vs-assume with a Definition of Ready, and ask only what a wrong guess would actually cost

中文简介正在准备中。当前显示原文说明。

Use when you create an implementation board task directly - the required fields, one-role-one-deliverable rule, and dependency ordering

中文简介正在准备中。当前显示原文说明。

Use when defining a feature - name what is in scope, out of scope, and assumed, and handle mid-flight expansion without corrupting in-progress tasks

中文简介正在准备中。当前显示原文说明。

Use when the stakeholder asks about an analysis outcome or its implementation tasks - understand the human approval gate and review the tasks the architect created once the human approved

中文简介正在准备中。当前显示原文说明。

Use when the stakeholder asks a factual or status question about the workspace - call the matching read tool and answer conversationally, without creating tasks or asking for approval

中文简介正在准备中。当前显示原文说明。

Use when opening an analiz task for the system-architect - the required fields, what the criteria may say, and what the description must hand over

中文简介正在准备中。当前显示原文说明。

Use when starting a mobile task that could be Flutter or native - decide from the existing app, platform-specific needs, and the analiz task

中文简介正在准备中。当前显示原文说明。

Use when a product decision or feature needs a written record - what to capture in a task document (PRD, decision record) and where to attach it, since TaskTrooper has no epic

中文简介正在准备中。当前显示原文说明。

Use when a task is in pm_uat - verify every acceptance criterion and the human's comments yourself in the browser, on a device, or over a loopback HTTP request, record a verdict per criterion, then move to human_uat or need_revision

中文简介正在准备中。当前显示原文说明。

Procedure for an analiz (analysis) task when you hold the analyst role. Use when a task with task_type analiz is assigned to you and add_task_document is in your tool list.

中文简介正在准备中。当前显示原文说明。

Test-first discipline and what makes a test worth keeping. Use when implementing any feature or bug fix, before writing production code, and whenever writing or changing a test.

中文简介正在准备中。当前显示原文说明。

Master workflow for an implementation task. Use when you pick up any task or bug that changes product code, including a need_revision bounce.

中文简介正在准备中。当前显示原文说明。

How to work a production incident remediation task. Use when the task title starts with "Incident:" or its description carries an incident id and a suggest/auto_fix policy.

中文简介正在准备中。当前显示原文说明。

Write board comments the way a colleague does — lead with the finding, a few lines, no preamble or process narration. Use when about to call add_task_comment or comment_on_pull_request, or when deciding whether something deserves a comment at all.

中文简介正在准备中。当前显示原文说明。

Rigorous engineering orchestrator ported from Lauren Tan's pstack (poteto-mode): reads your task, picks one of 23 playbooks (bug fix, feature, refactoring, perf, investigation, prototype, babysit, shipping, autonomous run, orchestrate, and more), routes to bundled procedures (how, why, architect, arena, swarm, interrogate, unslop, technical-writing, show-me-your-work, tdd, and others), and applies 24 engineering principles. Self-contained: no plugin install, no sibling skills required, works with any agent that reads skills.sh-format SKILL.md files. Use whenever a task needs rigor: nontrivial code changes, architecture decisions, debugging, reviews, PRs, long autonomous runs, or "work like poteto", "poteto-mode", "pstack".

中文简介正在准备中。当前显示原文说明。

Automated iterative agent runner for spec-based development in Kiro. Wraps kiro-cli in a self-correcting bash loop that picks up tasks from a Kiro spec, implements them one at a time, verifies against exit criteria, and accumulates corrections and codebase patterns across iterations. Use this skill when the user mentions "ralph loop", "ralph", "spec loop", "iterative spec runner", "run my spec tasks automatically", "kiro spec automation", "self-correcting agent loop", "implement spec tasks in a loop", "run kiro-cli in a loop", "automated task implementation", or wants to drive a Kiro spec to completion through repeated agent iterations. Also use when the user wants to set up, configure, troubleshoot, or understand the Ralph Loop workflow — including progress tracking, corrections, codebase patterns, timing logs, and the summary dashboard.

中文简介正在准备中。当前显示原文说明。

Write and edit Brazilian Portuguese prose with natural rhythm and the author's voice while preserving facts, meaning, and intent. Use for PT-BR requests to humanizar, tirar cara de IA, remover AI slop, reescrever com voz, simplify language, or write a post, email, article, or bio. Also use the author's notes or transcripts and ask targeted questions when essential facts are missing. For English text, use the bundled human-ai skill.

中文简介正在准备中。当前显示原文说明。

Create comprehensive implementation plans with bite-sized tasks. Use when you have requirements before touching code.

中文简介正在准备中。当前显示原文说明。

Summarize meetings using IDEAS framework - Insights, Decisions, Engagements, Actions, Summary. Use after any meeting.

中文简介正在准备中。当前显示原文说明。

Sync new Granola meetings to local Knowledge folder. Use during daily planning, when user asks "what should I do today", or asks to review/sync meetings.

中文简介正在准备中。当前显示原文说明。

Check Google Calendar for today's schedule. Use during daily planning or when user asks about their calendar.

中文简介正在准备中。当前显示原文说明。

Sync Jira issues with local tasks. Use during daily planning or when user asks about Jira issues.

中文简介正在准备中。当前显示原文说明。

Sync new Granola meetings to local Knowledge folder. Use during daily planning, when user asks "what should I do today", or asks to review/sync meetings.

中文简介正在准备中。当前显示原文说明。