rpraharaj/forward-deployed-engineer
Plugin Claude Code
Forward Deployed Engineer core skills: land in an unfamiliar organization and carry work from requirement to go-live, on any stack.
rpraharaj/forward-deployed-engineer
Skill Claude CodeCodex
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 for what is blocked, and keep a queue of useful work that does…
rpraharaj/forward-deployed-engineer
Skill Claude CodeCodex
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 to verify. Use before any non-trivial change, when asked…
rpraharaj/forward-deployed-engineer
Skill Claude CodeCodex
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 early in any engagement that will reach production, when a…
rpraharaj/forward-deployed-engineer
Skill Claude CodeCodex
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 behavior-preserving. Use before modifying code with thin or no test…
rpraharaj/forward-deployed-engineer
Skill Claude CodeCodex
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, define a working set, and hand off cleanly when context runs low.…
rpraharaj/forward-deployed-engineer
Skill Claude CodeCodex
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 feasibility and estimation exist and someone wants an order of work…
rpraharaj/forward-deployed-engineer
Skill Claude CodeCodex
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 first deploy of anything new or risky, when a release needs a…
rpraharaj/forward-deployed-engineer
Skill Claude CodeCodex
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 team must continue without you, when you have been building…
rpraharaj/forward-deployed-engineer
Skill Claude CodeCodex
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 proxies, start required services, and record every workaround…
rpraharaj/forward-deployed-engineer
Skill Claude CodeCodex
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 believe is not deliverable. Use as soon as you know, not…
rpraharaj/forward-deployed-engineer
Skill Claude CodeCodex
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 when asked how long something will take, when a date is being…
rpraharaj/forward-deployed-engineer
Skill Claude CodeCodex
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 an unfamiliar team, being assigned to a project you know…
rpraharaj/forward-deployed-engineer
Skill Claude CodeCodex
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 spec exists and before anyone estimates, commits to a date…
rpraharaj/forward-deployed-engineer
Skill Claude CodeCodex
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 deleting anything odd, when a constant or special case has no…
rpraharaj/forward-deployed-engineer
Skill Claude CodeCodex
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 another team, when someone else will take over work in progress…
rpraharaj/forward-deployed-engineer
Skill Claude CodeCodex
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 one you are doing. Use when production is broken, an alert…
rpraharaj/forward-deployed-engineer
Skill Claude CodeCodex
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 a system you do not, when the code cannot answer a…
rpraharaj/forward-deployed-engineer
Skill Claude CodeCodex
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 something you can actually test. Use before building anything…
rpraharaj/forward-deployed-engineer
Skill Claude CodeCodex
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 they were measured under. Use before release when NFRs have…
rpraharaj/forward-deployed-engineer
Skill Claude CodeCodex
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 you need a reviewer, an approver, or an interview subject…
rpraharaj/forward-deployed-engineer
Skill Claude CodeCodex
Assemble an evidence-based go/no-go position for a release - gather what prior artifacts already established, assess each readiness dimension as green, amber or red, state the recommendation together with the residual unknowns, and format it to survive a change advisory board. Use when approaching go-live, when a…
rpraharaj/forward-deployed-engineer
Skill Claude CodeCodex
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 plus a working CLAUDE.md. Use when dropped into a codebase you…
rpraharaj/forward-deployed-engineer
Skill Claude CodeCodex
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 handed an ambiguous requirement, a one-line ticket, a feature…