aperep/dev
A small development workflow with Occam-driven solution design, requirements, implementation, debugging, verification, review, and authorized delivery.
Audit a whole repository only for over-engineering: rank what to delete, simplify, or replace with stdlib or native features. Use for explicit requests to audit for over-engineering, find bloat, or identify what can be deleted across a codebase. Do not use for correctness, security, performance, or diff-only review.
Investigate bugs, regressions, failing tests, or broken behavior by tracing evidence to the root cause, then implement and verify a scoped fix when requested. For explanation-only requests, diagnose without editing. Does not handle new feature design or commit-message-only requests.
Govern an end-to-end development change from a safe start through requirements, investigation, implementation, and verified delivery. Use when asked to begin, perform, resume, or finish a code change, including explicit Ponytail, YAGNI, or simplest-solution requests that change code. Do not use for review-only, verification-only, or commit-message-only requests.
Clarify feature requirements, pressure-test scope and domain terms, and produce a feature spec before implementation. Use for fuzzy requirements, PRD/spec requests, 需求对齐, 拷问需求, or 设计文档. Read existing evidence before asking focused questions. A generic "do not edit code" instruction alone does not trigger intake. Supports --quick, --deep, and --spec-only.
Review a requested Git diff for correctness risks, unnecessary complexity, or both. Use for review requests and the review phase of commit requests; infer the requested lens from bugs/regressions versus over-engineering/deletion language. Do not use for whole-repository audits, verification-only requests, or commit-message-only requests.
Implement scoped behavior changes using meaningful tests before code where practical. Use for features, behavior-preserving refactors, and direct fixes with a known cause; use debug for bug investigation. Documentation, formatting, and asset-only edits do not need this coding workflow.
Verify implemented changes before claiming they are complete, fixed, passing, or ready for delivery. Match checks to requested behavior and risk, inspect current evidence, and report limits. Use for completion checks, not general factual answers or a replacement for code review.