Skip to content

Tagged AgentDocs

14 agentdocs tagged

fromobra

Finishing a Development Branch

Overview Guide completion of development work by presenting clear options and handling chosen workflow. Core principle: Verify tests → Present options → Execute choice → Clean up. Announce at start:...

@obra·
5h ago
·
375 words

Executing Plans

Overview Load plan, review critically, execute all tasks, report when complete. Announce at start: "I'm using the executing-plans skill to implement this plan." Note: Tell your human partner that...

@obra·
5h ago
·
317 words

Using Git Worktrees

Overview Git worktrees create isolated workspaces sharing the same repository, allowing work on multiple branches simultaneously without switching. Core principle: Systematic directory selection +...

@obra·
5h ago
·
386 words

Dispatching Parallel Agents

Overview You delegate tasks to specialized agents with isolated context. By precisely crafting their instructions and context, you ensure they stay focused and succeed at their task. They should...

@obra·
5h ago
·
410 words

Verification Before Completion

Overview Claiming work is complete without verification is dishonesty, not efficiency. Core principle: Evidence before claims, always. Violating the letter of this rule is violating the spirit of...

@obra·
5h ago
·
371 words

Subagent-Driven Development

Execute plan by dispatching fresh subagent per task, with two-stage review after each: spec compliance review first, then code quality review. Why subagents: You delegate tasks to specialized agents...

@obra·
5h ago
·
393 words

Requesting Code Review

Dispatch superpowers:code-reviewer subagent to catch issues before they cascade. The reviewer gets precisely crafted context for evaluation — never your session's history. This keeps the reviewer...

@obra·
5h ago
·
303 words

Writing Plans

Overview Write comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each...

@obra·
5h ago
·
918 words

Systematic Debugging

Systematic Debugging Overview Random fixes waste time and create new bugs. Quick patches mask underlying issues. Core principle: ALWAYS find root cause before attempting fixes. Symptom fixes are...

@obra·
5h ago
·
1513 words

Using Superpowers

<SUBAGENT-STOP> If you were dispatched as a subagent to execute a specific task, skip this skill. </SUBAGENT-STOP> <EXTREMELY-IMPORTANT> If you think there is even a 1% chance a skill might apply to...

@obra·
5h ago
·
786 words

writing-skills

Writing Skills Overview Writing skills IS Test-Driven Development applied to process documentation. Personal skills live in agent-specific directories (/.claude/skills for Claude Code,...

@obra·
5h ago
·
3220 words

Receiving Code Review

Code Review Reception Overview Code review requires technical evaluation, not emotional performance. Core principle: Verify before implementing. Ask before assuming. Technical correctness over social...

@obra·
5h ago
·
406 words

Test-Driven Development

Test-Driven Development (TDD) Overview Write the test first. Watch it fail. Write minimal code to pass. Core principle: If you didn't watch the test fail, you don't know if it tests the right thing....

@obra·
5h ago
·
562 words

Brainstorming

Brainstorming Ideas Into Designs Help turn ideas into fully formed designs and specs through natural collaborative dialogue. Start by understanding the current project context, then ask questions one...

@obra·
5h ago
·
1549 words