effective-tasks

Write self-contained SIMBL task briefs by embedding Context, Requirement, Snippet, and Acceptance Criteria directly into the task. Include explicit file paths, function references, error messages, and precise acceptance criteria formatted in markdown blocks so the agent can parse and execute reliably without asking follow-up questions.

Use SIMBL task structure: craft precise titles, embed relevant code snippets and error messages, state clear requirements, and define concrete acceptance criteria. Apply priority tags (p1-p9) and status tags (in-progress, canceled) consistently across your workflow to ensure team alignment and reduce rework.

Vague task descriptions cause delays and repeated work. Structure tasks with embedded context, code references, and explicit acceptance criteria so execution happens on first attempt. This approach eliminates back-and-forth clarification and accelerates development cycles across diverse codebases.

Yes. Create a SIMBL task by specifying the function name and file path, describing the bug or crash behavior, including the current code snippet, stating the fix requirement, and defining how to verify the fix works. This format gives Claude or your team all context needed to resolve the issue immediately.

Embed the code snippet causing the issue, the error message or observed behavior, related file paths, the business or technical requirement, and explicit acceptance criteria. SIMBL tasks work best when they include enough detail that the executor never needs to ask for clarification.

Use priority tags (p1-p9) to signal urgency and status tags (in-progress, canceled) to communicate task state to your team. These tags improve task tracking, help prioritize work in agile sprints, and ensure visibility across documentation and project workflows.