메뉴
SkillsMP는 rpraharaj/forward-deployed-engineer에서 43개의 skill을 수집했습니다. skill을 열어 소스와 세부 정보를 확인하세요.
수집된 skill 43개 중 40개를 표시합니다.
Turn getting access into a tracked critical path instead of a passive wait. Enumerate every credential, permission, environment, and account the engagement needs, identify who approves each and its lead time, request long-lead items first, find workarounds…
원문 언어: 영어
Map everything a proposed change could break before making it - direct callers, cross-repository consumers, published contracts, event subscribers, feature flags, shared database objects, and config coupling - ending with a risk rating and the specific things…
원문 언어: 영어
Find and work with the organization's change process before it blocks you - which gates apply, what evidence each requires, submission deadlines, freeze periods, release calendars, and segregation of duties - then work backwards from the release window. Use…
원문 언어: 영어
Pin the current behavior of untested legacy code before changing it - including behavior that looks like a bug, because something downstream may depend on it - using golden master and approval test patterns so a refactor or fix can be verified as…
원문 언어: 영어
Work effectively in a codebase far larger than any context window, across an engagement that spans many sessions. Decide what to read versus search versus script versus delegate, build a durable CLAUDE.md so each session does not re-derive the same map,…
원문 언어: 영어
Sequence work by risk rather than convenience - unknowns first so bad news arrives early, slices that are independently shippable, dependencies on other teams surfaced with lead times, and an explicit statement of what would change the plan. Use once…
원문 언어: 영어
Write the executable deployment procedure - pre-checks, ordered steps, what to observe after each, the specific conditions that trigger a rollback, and the rollback procedure itself - so that someone who is not the author can run it at 2am. Use before the…
원문 언어: 영어
Teach the receiving team to operate and extend what you built, rather than only documenting it - pairing, walkthroughs, deliberately leaving work for them to finish, and confirming they can actually run it without you. Use when an engagement is ending and the…
원문 언어: 영어
Get a working build, test, and run loop in an unfamiliar repository on a locked-down machine - read the CI config as ground truth for how the software is actually built, check toolchain versions against the repo's pins, configure internal registries and…
원문 언어: 영어
Raise a problem early with evidence and a recommendation, or reopen scope without losing credibility - when the plan is no longer achievable, a dependency is not moving, the requirement turns out to be wrong, or you are being asked to commit to something you…
원문 언어: 영어
Size work under genuine uncertainty, grounded in feasibility findings rather than optimism - ranges rather than points, explicit assumptions, the organizational overheads engineers routinely forget, and a clear statement of what would move the number. Use…
원문 언어: 영어
Open a new engagement as a forward deployed engineer - establish what you have actually been asked to do, classify the engagement type, set up the .fde workspace, and produce a sequenced plan of which skills to run. Use when starting at a new client, joining…
원문 언어: 영어
Ground a specification in the actual codebase - for each requirement establish whether the capability already exists, exactly where a change would land, what shape the change takes, what is missing entirely, and which items look cheap but are not. Use after a…
원문 언어: 영어
Recover intent from history when code looks wrong - blame to commit to pull request to linked ticket, plus revert and hotfix patterns - so you find out why something is the way it is before removing it. Use when code looks unnecessary or bizarre, before…
원문 언어: 영어
Consolidate an engagement into what the receiving team actually needs - refreshed CLAUDE.md, runbooks, ADRs, known issues, and explicitly the open risks and unfinished business that most handovers omit. Use when an engagement is ending, when rotating to…
원문 언어: 영어
Work backward from a production symptom to its cause under time pressure - stack trace to source, correlation IDs across services, log and metric narrowing, recent-change correlation - while prioritizing mitigation over root cause and saying explicitly which…
원문 언어: 영어
Extract what only a person knows - structured preparation and questioning for a short session with a long-tenured engineer, system owner, or business expert, then conversion of what you learn into cited artifacts. Use before or after meeting someone who knows…
원문 언어: 영어
Make non-functional requirements explicit and measurable before build starts - latency and throughput targets, data sensitivity classification, audit and retention obligations, observability needs, and failure and degradation behavior - each written as…
원문 언어: 영어
Actually measure the non-functional requirements rather than asserting them - performance under realistic load, behavior at failure boundaries, and whether the audit logging exists and contains what it should - reporting measured numbers with the conditions…
원문 언어: 영어
Work out who owns what and who decides, from evidence rather than the org chart - CODEOWNERS, commit authorship over time, review patterns, ticket references, and directory-level activity - distinguishing who wrote the code from who maintains it now. Use when…
원문 언어: 영어
Build a breadth-first map of an unfamiliar codebase in a bounded amount of time - entry points, module boundaries, persistence and integration surface, churn hotspots, test topology, config surface, and landmines - then write it up as a durable system map…
원문 언어: 영어
Turn a vague ask into a testable specification - separate the stated request from the underlying need, write acceptance criteria as observable behavior, state what is explicitly out of scope, and record every assumption with who can confirm it. Use when…
원문 언어: 영어
Implement an already-specified change in an unfamiliar or high-stakes codebase with the smallest viable diff - establish a green baseline first, match the surrounding idiom rather than importing your own, separate refactor commits from behavior commits, gate…
원문 언어: 영어
Review a change specifically for data handling before release - what sensitive data crosses this path, whether it is logged or cached, encryption in transit and at rest, secrets externalized, and whether the audit trail satisfies the stated obligation. Use as…
원문 언어: 영어
Translate the current technical position into something a busy non-engineer reads in ninety seconds - what changed, what it means, what decision is needed, what the risk is - pitched at the right register for the reader. Use at every phase boundary rather…
원문 언어: 영어
Get realistic test data in an organization where production data cannot be copied - synthesis, subsetting, masking with referential integrity preserved, and fixtures for the awkward edge cases that only real systems produce. Use when tests need data you do…
원문 언어: 영어
Map every acceptance criterion to the specific evidence that proves it - which test, which manual check, which measurement - and surface the gap list of criteria with no verification at all. Use once implementation is underway, before claiming anything is…
원문 언어: 영어
Reconstruct an undocumented data model from whatever exists - migrations, DDL, ORM definitions, and most reliably the queries actually issued - then surface the gap between the schema's stated intent and its real use. Use when a schema is undocumented, when…
원문 언어: 영어
Build or change ETL, ELT, warehouse, and reporting pipelines where the failure modes are silent - data quality decay, late-arriving and duplicate records, backfill and reprocessing, idempotency, lineage, and reconciliation against a source of truth. Use for…
원문 언어: 영어
Change a schema against a live production database without taking an outage - expand and contract patterns, zero-downtime DDL, lock and replication-lag behavior on large tables, reversibility, and coordinating the migration with the application deploy that…
원문 언어: 영어
Plan the moment two systems swap - data migration and backfill, dual-run and reconciliation, the consistency window, traffic shifting, the point of no return, and what abort means at each stage. Use for any migration or replatform where data moves and both…
원문 언어: 영어
Turn a system off safely - proving there are no remaining consumers, which is much harder than it sounds, then data retention and archival obligations, a staged darkening sequence, and how long to keep the ability to reverse. Use when a system is being…
원문 언어: 영어
Run an EOL or version-driven upgrade where the scope is fixed, the deadline is external, and the risk is concentrated in transitive breakage - ordering the upgrade, building a compatibility matrix, cutting over incrementally, and telling a real break from a…
원문 언어: 영어
Change code that must change but is not safely changeable - find the seams that let you alter behavior without rewriting, using branch-by-abstraction, strangler fig, and adapter insertion, always leaving the system releasable at every step. Use when…
원문 언어: 영어
Diagnose a red, flaky, or slow pipeline by identifying the failure class first - genuine break, flake, environment drift, ordering dependency, or resource contention - before attempting fixes, and distinguishing making it green from making it right. Use when…
원문 언어: 영어
Ask whether a failure could have been seen, then close the gaps - missing logs, metrics, traces, and alerts - so the next incident is cheaper to diagnose. Use after any incident where the answer was hard to find, before shipping anything whose failure would…
원문 언어: 영어
Define and execute the observation window after a release - smoke checks, the specific metrics that would show this change broke something, how long to watch, and pre-agreed rollback triggers - converting "seems fine" into a recorded verification. Use…
원문 언어: 영어
Design an API, event, or schema contract with compatibility as the primary concern - versioning strategy, backward compatibility, migration path for existing consumers, and failure semantics - plus a consumer impact list. Use when creating or changing…
원문 언어: 영어
Work on a vendor platform where the deliverable is configuration rather than code - SAP, Salesforce, ServiceNow, Workday, Dynamics, Guidewire and similar - where the binding constraint is the vendor upgrade path, config lives in the platform rather than in…
원문 언어: 영어
Build a client against a system you do not control and cannot fully see - contract discovery from observed traffic and existing callers, defensive parsing, timeout and retry and circuit-breaking posture, and a fake for testing. Use when consuming a legacy,…
원문 언어: 영어