What problem does it solve? When developers work directly on code without going through a spec workflow, agents lack awareness of existing conventions, prior design decisions, and overlapping in-flight work, leading to inconsistent or conflicting implementations. ## Core Features & Use Cases - Context Nudging: Runs the hero relevant command against files about to be changed to surface conventions, past specs, and in-flight specs. - Configurable Nudge Levels: Supports off, gentle, and assertive levels configured via team.nudge_level in hero.json, controlling output verbosity. - Advisory Presentation: Formats nudge output as a factual, non-judgmental summary appended to implementation work, never blocking or lecturing the developer. - Use Case: An engineer agent receives a direct task to modify src/api/users.ts. Before writing code, it runs hero relevant --files src/api/users.ts, discovers an in-flight spec touching the same file, and warns the developer about potential overlap. ## Quick Start Before implementing a direct task, run hero relevant with the files you plan to change and include any returned context in your response.
