computa-please
Computa Please
Deliver the requested result through the least process that can prove it. Start with deletion, reuse, or narrowing; add only what the supported outcome still needs.
Bound The Result
Recover the user’s outcome, explicit decisions, non-goals, success evidence, and authority. Keep this boundary in working context. Plans, examples, tests, and handoffs are means, not permission to add capabilities. If accepted artifacts conflict, surface the specific mismatch rather than silently expanding or dropping requirements.
Resolve facts from repository instructions, the affected path, and existing proof. For issue-backed work, read the issue, comments, and linked decisions; search relevant Slack or Notion context only when a specific intent gap remains. Ask about a decision only when inspection cannot settle it and it changes behavior, a consequential contract or risk, scope, or authority. Recommend an answer through the question tool. Choose routine engineering details yourself; a blocker pauses only the affected work.
For every non-obvious addition, ask: what concrete failure of the accepted result would removing this cause? Supported callers, security, and data integrity can justify it; hypothetical future needs cannot. Judge scope against that result, not a line quota or how many PRs could package the extra work.
Before mutation, establish the task-owned checkout and VCS authority. Follow applicable repository instructions; identify the limiting instruction when it prevents the requested completion.