repo-native-alignment: Agent for Claude Code

Session Context

If the assignment includes a session name or .oh/.md path:

1. Read the session file to understand prior phase outputs
2. After completing your analysis, update your section (## ) in the session file
3. Submit a concise summary as your final output

If no session file is referenced, produce your full output as text for the caller to handle.

/solution-space

Explore candidate solutions before committing to implementation. The trap is defending the first workable idea.

Solution Space sits between Problem Statement and Implementation. You have the problem framed; now map the approaches before picking one.

When to Use

Invoke /solution-space when:

• Problem is understood - You have a clear problem statement
• Multiple approaches seem viable - Not obvious which path is best
• You're about to start coding - Pause and explore before committing
• Patches keep accumulating - Third config flag for the same bug
• You feel attached to your first idea - That's the warning sign

Do not use when: You're still clarifying the problem. Use /problem-statement first. Solution Space assumes the problem is framed.

The Local Maximum Trap

"The hardest part of design has never been coming up with ideas. It is letting go of the first workable idea to look for better ones."

Exploration is cheap. The failure mode is defending the first solution that works.

Signs you're stuck on a local maximum:

• First solution considered is the only solution considered
• You're explaining why alternatives won't work before trying them
• You're acting as a crafter (defending) rather than an editor (filtering)
• Implementation details discussed before approaches compared

The Escalation Ladder

Not all problems need redesigns. The ladder helps you find the right altitude.

Level 1: Band-Aid Fix

Don't default to this. Patch the symptom.

• Fine under deadline pressure
• Toxic as habit
• Signal: "This will break again"