zhuochun
- 35 skills
- 0 followers
- 7 hours ago last updated
- ▌ Code Review · zhuochun bundleReview a proposed or completed software change against its intent, constraints, supported behavior, evidence, and future change cost without modifying it. Use for working-tree, commit, branch, pull-request, generated-code, migration, or configuration review before merge or release. Route whole-architecture scenarios to architecture-risk-evaluation and portfolio diagnosis to architecture-assessment.
- ▌ Domain Modeling · zhuochun bundleDiscover, compare, and evolve selective software domain models and bounded contexts around an important problem. Use when solution-shaped requirements, conflicting language, repeated exceptions, disputed concepts, classifications, or invariants, unclear translations, or hidden historical state make behavior hard to express. Model meaning before choosing services, schemas, deployment boundaries, or object patterns.
- ▌ Incident Learning · zhuochun bundleFacilitate or analyze incidents, outages, near misses, and operational surprises as system-learning reviews. Use for postmortems, debriefs, recurring failures, weak-signal analysis, or follow-up quality reviews. Reconstruct timelines and local reasoning, expose model and control gaps, preserve successful adaptations, and create durable improvements without blame or premature root-cause closure.
- ▌ Technical Writing · zhuochun bundleWrite or revise task-fit technical documentation and evidence-grounded articles from supplied sources, code, and observed behavior. Use for tutorials, how-to guides, durable explanations, reference, runbooks, procedures, technical blogs, AI-slop audits, or humanizing and voice-preserving edits. Route engineering mental-model clarification to technical-growth-coaching, cross-source evidence to research-synthesis, skill authoring to skill-creator, and unresolved domain decisions to their owners.
- ▌ Deep Module Design · zhuochun bundleDecide whether to retain or redesign a software module or interface before implementation. Use when a request asks where a seam belongs, whether duplication should gain one owner, how to deepen a shallow abstraction, make dependencies testable, or add a new variant without leaking policy. Do not use for an accepted implementation or behavior-preserving refactor.
- ▌ Migration Planning · zhuochun bundlePlan a survivable technical migration from an established state to an accepted replacement while supported obligations continue. Use when state, traffic, consumers, execution, infrastructure, or authority must move and the old state must become retireable. Own transition states, authority transfer, cutover, retreat or compensation, retireability, and retirement; route target, contract, ownership, and program decisions.
- ▌ Prototype To Learn · zhuochun bundleBuild a disposable, runnable software prototype that answers one explicit behavior, state, UI, or interaction design question before maintained implementation. Use when users want to compare runnable candidates, exercise an interaction direction before choosing maintained behavior, or drive candidate rules or state models through cases. Route customer-value experiments to product-opportunity-discovery and production changes to scoped-change-implementation.
- ▌ Research Synthesis · zhuochun bundleProduce a bounded cross-source synthesis of what high-trust evidence supports, contradicts, or leaves unresolved, with claim provenance, applicability, confidence, and gaps. Use for literature reviews and comparisons across papers, standards, reports, guidance, or datasets. Exclude one-source summaries, current-system orientation, local domain modeling, regulated applicability, verification design or execution, and downstream recommendations or decisions.
- ▌ Observability Design · zhuochun bundleDesign or audit decision-oriented observability across outcomes, behavior, dependencies, infrastructure, ownership, and control paths. Use before rollout for signals, dashboards, alerts, SLOs, correlation, or release evidence, and after representative operation to test whether telemetry supports orientation, diagnosis, routing, recovery, and learning. Exclude live incident command and verification verdicts.
- ▌ Specification Review · zhuochun bundleIndependently review a specification, RFC, requirements set, behavioral contract, or decision-bearing proposal for contradictions, ambiguity, hidden decisions, unsupported claims, missing boundaries or failure behavior, and wording loopholes before implementation or adoption. Work read-only and return prioritized findings and readiness limits; route architecture fitness, product evidence, domain meaning, editorial quality, and code changes to their owners.
- ▌ Decision Facilitation · zhuochun bundleFacilitate a consequential or contested decision from unclear intent to explicit authority, alternatives, evidence, assumptions, tradeoffs, closure, and follow-through. Use for organizational, product, operational, or technical choices, recurring reopening, proposal preparation, or requests to grill, challenge, or stress-test a decision. Keep reversible choices lightweight and route specialist analysis to its owner.
- ▌ Software Verification · zhuochun bundleDesign or execute risk-proportionate software verification by binding engineering claims to fixed methods, oracles, environments, and inspectable evidence. Use for architecture testing, undefined coverage, stale or missing evidence, named claims that must run, or an independent final check. Keep inner-loop feedback, fresh-context verification, design decisions, and release authority distinct.
- ▌ Software System Design · zhuochun bundleDesign a coherent technical solution for a bounded software capability or system when responsibilities, state ownership, interfaces, and execution must be resolved together across an end-to-end path. Use for new capabilities, application architecture, or integrations with unsettled structure. Keep settled implementation and isolated module decisions with their owners; do not implement or certify the design.
- ▌ Architecture Assessment · zhuochun bundleDiscover and rank architecture improvement opportunities across an existing software scope before one redesign target is selected. Use for portfolio health checks, accumulated architecture drift, fresh-eye reassessment, modernization priorities, fragile hotspots, testing difficulty, or ownership friction. Route one proposal to architecture-risk-evaluation, completed-design learning to retrospective-architecture-review, and architecture testing to software-verification.
- ▌ Service Boundary Design · zhuochun bundleDecide whether deployable service boundaries should be kept, split, merged, strengthened, or replaced by an in-process module boundary. Use for microservice proposals, modular-monolith reviews, service sprawl, unclear data ownership, cross-service pain, incidents, or ownership realignment. Ground recommendations in domain, change, data, runtime, failure, and operating evidence; route module details to deep-module-design.
- ▌ Agentic Repo Environment · zhuochun bundleDiagnose, bootstrap, retrofit, or renew the repository-local environment for reliable coding-agent work. Use read-only diagnosis for task-path gaps, Bootstrap for minimum working paths, Retrofit for observed friction, and Renew for accepted corrections that may generalize. Route product meaning, architecture decisions, command compatibility, and release authority to their owners.
- ▌ Service Ownership Design · zhuochun bundleDesign or assess whether a team and its enabling environment can sustainably own a production service across delivery, operation, support, improvement, and retirement. Use before ownership transfer, expanded full-cycle responsibility, reduced handoffs, on-call change, or review of nominal ownership. Exclude headcount justification, work dumping, and unsafe consolidation of regulated or high-risk duties.
- ▌ Software Security Design · zhuochun bundleDesign or revise a change-level secure-by-design contract across delivery. Use for threat modeling or when attacker-controlled inputs, protected data or effects, identity, secrets, dependencies, tenant boundaries, privilege, AI agents, or unsafe defaults create material security decisions. Produce prioritized threat paths, security requirements, secure defaults, control ownership, assurance obligations, and residual-risk routes; exclude organization-wide security-program assessment.
- ▌ Controlled Release Design · zhuochun bundleDesign controlled exposure for changing behavior through flags, dark launches, canaries, cohorts, kill switches, and release evidence. Use when deployment must be separated from exposure or promotion, abort, mixed states, ownership, and cleanup need explicit control. Use migration-planning as the enclosing plan when an established technical state must move, lose authority, and become retireable.
- ▌ Technical Growth Coaching · zhuochun bundleHelp an engineer, technical lead, or team improve judgment by diagnosing the learning gap, adapting explanation or practice, and using feedback to test transfer. Use for technical misconceptions, mentorship, onboarding, stretch assignments, or stalled expertise. Keep bounded explanations compact; exclude general tutoring, document production, performance ratings, promotion, compensation, and formal employee-support processes.
- ▌ Platform Capability Design · zhuochun bundleDesign or review internal platform capabilities that turn repeated engineering work into honest, self-service, supportable paths with useful defaults, guardrails, and escape hatches. Use for developer platforms, paved roads, service templates, platform APIs, ticket-heavy services, or duplicated tooling. Do not use merely to centralize ownership, select a vendor, or prescribe team topology.
- ▌ Software Failure Diagnosis · zhuochun bundleDiagnose bugs, regressions, intermittent failures, incorrect results, crashes, and performance degradation by turning symptoms into discriminating evidence and a supported cause. Use first whenever a newly reported symptom remains unexplained, even when the user also authorizes a fix. After causal support, route the bounded repair to scoped-change-implementation.
- ▌ Software Contract Evolution · zhuochun bundleDesign how software contracts evolve while independently changing producers, consumers, and stored state coexist. Use for APIs, events, schemas, protocols, libraries, commands, or integrations involving compatibility, versioning, deprecation, translation, mixed versions, or retirement. Recover the actual support promise, compare evolution options, define adoption obligations, and require risk-specific evidence before removal.
- ▌ Architecture Risk Evaluation · zhuochun bundleEvaluate software architecture by translating business drivers and quality goals into prioritized, falsifiable scenarios and tracing them through components, data, deployment, dependencies, and operating procedures. Use for architecture proposals, design reviews, modernization programs, major technology choices, vague scalability or availability claims, cross-team tradeoffs, or ADR preparation before consequential decisions harden.
- ▌ Architecture Surface Mapping · zhuochun bundleOrient across multiple architecture surfaces of unfamiliar software or trace one bounded end-to-end journey across experience, operations, domain state, systems, data, interfaces, and owners. Use when a decision depends on cross-surface relationships or expected and observed paths disagree. Keep simple lookups direct; route architecture judgment, product discovery, and redesign elsewhere.
- ▌ Scoped Change Implementation · zhuochun bundleImplement a ready, authorized, bounded feature, enhancement, integration, configuration change, or causally supported fix in coherent vertical slices while preserving conventions, unrelated work, behavior, and controls. Fix authority does not establish cause; route unexplained failures to software-failure-diagnosis, pure structure to behavior-preserving-refactoring, and disposable learning to prototype-to-learn.
- ▌ Service Capacity Engineering · zhuochun bundleModel, design, or review end-to-end service capacity and behavior near or beyond saturation across online, asynchronous, batch, storage, or shared workloads. Use for peak readiness, nonlinear latency, queue growth, retries, fan-out, noisy neighbors, failover headroom, load tests, admission control, backpressure, or shedding. Exclude complete cloud-cost optimization and financial forecasting.
- ▌ Product Opportunity Discovery · zhuochun bundleDiscover and test which customer opportunity and solution direction merits investment before heavy implementation. Use for solution-shaped feature requests, conflicting customer evidence, opportunity models, assumption mapping, prototypes, experiments, or comparisons among solutions. Produce an evidence-based learn, narrow, pivot, stop, or proceed recommendation; exclude roadmap allocation and implementation of accepted work.
- ▌ Software Change Specification · zhuochun bundleSpecify an accepted but ambiguous software change before implementation by recovering current and desired behavior, scope, invariants, affected surfaces, acceptance claims, and unresolved decisions. Use when implementers would otherwise invent consequential behavior. Do not use to review a fixed candidate; use specification-review. Keep small clear changes in scoped-change-implementation; route unresolved specialist decisions to their owners.
- ▌ Incident Response Coordination · zhuochun bundleCoordinate live software incident response through accountable command, customer-impact stabilization, delegated workstreams, communications, evidence preservation, and deliberate recovery handoff. Use during outages, severe degradation, multi-service incidents, escalation, or response confusion. Support a human incident commander; do not claim command authority or execute risky mitigation without explicit delegation or a tested, pre-authorized bounded runbook.
- ▌ Behavior Preserving Refactoring · zhuochun bundleImprove software structure while preserving supported observable behavior, compatibility, and operational semantics. Use for an authorized module redesign, legacy seam, abstraction extraction or collapse, ownership move, coupling reduction, or learned-architecture consolidation without intended behavior change. Route intentional behavior changes to scoped-change-implementation and undecided retrospective redesign to retrospective-architecture-review.
- ▌ Experience Design Specification · zhuochun bundleDesign a reviewable user experience for an intended outcome through user-facing concepts, task flows, information hierarchy, interaction states, feedback, and recovery. Use before implementation when people would otherwise invent consequential UX choices. Route opportunity validation to product discovery, fixed-candidate review to specification-review, and small clear edits directly to implementation.
- ▌ Technical Program Orchestration · zhuochun bundleOrchestrate one accepted technical outcome across concurrent or interdependent workstreams, vertical increments, integration, evidence, replanning, and closure. Use only when distinct drivers need shared steering across dependencies, integration points, decisions, or constraints. Do not use for generic goal pursuit, serial specialist routing, one bounded delivery loop, or multiple teams without coordination topology.
- ▌ Retrospective Architecture Review · zhuochun bundleReconsider one completed software design after implementation, repeated change, operation, incidents, support, or ownership creates a material knowledge delta. Recover commitments, compare alternatives, and recommend retain, quarantine, prune, reshape, or rebuild without modification. Exclude portfolio discovery, routine implementation review, weak first design passes, and already-decided refactors; use architecture-assessment for broad investment ranking.
- ▌ Product Opportunity Prioritization · zhuochun bundlePrioritize product opportunities and bets against explicit outcomes, strategy, customer evidence, obligations, capacity, dependencies, risk, and learning horizon. Use for outcome roadmaps, reframing feature backlogs, choosing among customer problems, balancing near-term and uncertain bets, or reviewing allocation. Exclude company-wide capital governance, discovery from scratch, and delivery sequencing after priorities are accepted.