Can it break down large tasks automatically?

Yes, it is designed to identify any task estimated at over 16 hours and guide the breakdown into 4-8 hour subtasks.

Does it modify my source code?

No, it specifically refines your Task objects and development plan structure within Claude Code to prevent errors before they reach the code.

How does it help junior engineers?

It ensures every task description is so detailed and clear that a junior developer won't need to ask clarifying questions during execution.

What is the Google Fellow SRE perspective?

It refers to a high-standard review style that prioritizes system reliability, deep failure mode analysis, and extreme clarity in technical requirements.

When should I use the Task Refinement skill?

Use it after brainstorming a feature but before starting implementation to ensure the plan is solid and handles all edge cases.

Task Refinement

Name: Task Refinement
Author: Veraticus

byVeraticus

Productivity & Workflow

Refines development plans with SRE-level scrutiny to ensure tasks are granular, edge-case-proof, and execution-ready.

About

The Task Refinement skill transforms high-level development plans into actionable, bulletproof workflows by applying a rigorous 8-category SRE checklist. Inspired by Google Fellow-level engineering standards, it identifies vague instructions, breaks down oversized tasks, and mandates specific success criteria to ensure even junior engineers can execute without ambiguity. Use this skill to catch production risks, verify test meaningfulness, and eliminate placeholders before a single line of code is written.

Key Features

Placeholder & Anti-pattern Detection
Automatic Task Granularity & Subtask Breakdown
SRE-Style 8-Category Review Checklist
Edge Case & Failure Mode Analysis
0 GitHub stars
Measurable Success Criteria Hardening

Use Cases

Reviewing complex feature plans before starting implementation
Ensuring tasks are clear enough for junior developers to execute independently
Identifying hidden production risks and concurrency edge cases in system designs

About

Key Features

Placeholder & Anti-pattern Detection
Automatic Task Granularity & Subtask Breakdown
SRE-Style 8-Category Review Checklist
Edge Case & Failure Mode Analysis
0 GitHub stars
Measurable Success Criteria Hardening

Use Cases

Reviewing complex feature plans before starting implementation
Ensuring tasks are clear enough for junior developers to execute independently
Identifying hidden production risks and concurrency edge cases in system designs