Skip to content
Back to search

fde-stack

MarketplaceWorks with Claude CodeGitHub

The fde skill: a forward-deployed engineer workflow for Claude Code.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/brandeispatrick--fde-stack/badge.svg)](/listings/brandeispatrick--fde-stack)

HTML

<a href="/listings/brandeispatrick--fde-stack"><img src="/api/listings/brandeispatrick--fde-stack/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

In Claude Code:

/plugin marketplace add BrandeisPatrick/fde-stack
/plugin install fde@fde-stack
/fde:fde progress

This runs against a bundled [sample project](skills/fde/sample-vault/README.md), so there is nothing to set up. You can also just ask: "how far along is Contoso?"

To use it on your own work, run `/fde:fde initialize` once per project.

<details> <summary>Install without the plugin</summary>

git clone https://github.com/BrandeisPatrick/fde-stack ~/code/fde-stack
mkdir -p ~/.claude/skills && ln -s ~/code/fde-stack/skills/fde ~/.claude/skills/fde

The command is then `/fde` instead of `/fde:fde`. Update with `git -C ~/code/fde-stack pull`.

</details>

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 14 lines
  1. {
  2. "name": "fde-stack",
  3. "owner": {
  4. "name": "BrandeisPatrick"
  5. },
  6. "description": "The fde skill: a forward-deployed engineer workflow for Claude Code.",
  7. "plugins": [
  8. {
  9. "name": "fde",
  10. "source": "./",
  11. "description": "Forward-deployed engineer workflow: catch up from a private vault, build with a team of agents, ship through PRs with diagrams."
  12. }
  13. ]
  14. }
README.md · README · 221 lines
  1. <h1 align="center">/fde</h1>
  2. <p align="center">
  3. <b>Run client projects as a forward-deployed engineer, with Claude Code.</b><br>
  4. Catch up in one message. Build with a team of agents. Ship every change as a reviewed PR.
  5. </p>
  6. <p align="center">
  7. <a href="https://github.com/BrandeisPatrick/fde-stack/releases"><img src="https://img.shields.io/github/v/release/BrandeisPatrick/fde-stack?color=444441" alt="Latest release"></a>
  8. <a href="https://github.com/BrandeisPatrick/fde-stack/actions/workflows/check.yml"><img src="https://github.com/BrandeisPatrick/fde-stack/actions/workflows/check.yml/badge.svg" alt="Checks"></a>
  9. <a href="LICENSE"><img src="https://img.shields.io/badge/license-MIT-444441.svg" alt="MIT license"></a>
  10. <img src="https://img.shields.io/badge/Claude%20Code-plugin-d97757.svg" alt="Claude Code plugin">
  11. </p>
  12. <p align="center">
  13. <a href="#quick-start">Quick start</a> ·
  14. <a href="#see-it-work">See it work</a> ·
  15. <a href="#how-it-works">How it works</a> ·
  16. <a href="#commands">Commands</a> ·
  17. <a href="#data-handling">Data handling</a> ·
  18. <a href="#faq">FAQ</a>
  19. </p>
  20. <table>
  21. <tr>
  22. <td width="50%" valign="top"><img src="docs/assets/screens/fde-progress.svg" alt="Claude Code reply to /fde progress: four workstreams with ten-cell bars."></td>
  23. <td width="50%" valign="top"><img src="docs/assets/screens/fde-recap.svg" alt="Claude Code reply to /fde recap: a verdict, a short table, a diagram and a proposal."></td>
  24. </tr>
  25. <tr>
  26. <td align="center"><code>/fde progress</code></td>
  27. <td align="center"><code>/fde recap</code></td>
  28. </tr>
  29. </table>
  30. ## What you get
  31. <table>
  32. <tr>
  33. <td width="33%" valign="top"><b>Catch up in one message</b><br>Code, deployment, access, what changed and what is yours. Every line links to its source.</td>
  34. <td width="33%" valign="top"><b>Build with a team of agents</b><br>Opus plans and reviews. Sonnet agents build in parallel, each in its own worktree.</td>
  35. <td width="33%" valign="top"><b>Ship reviewed PRs</b><br>Every change lands as a PR with a diagram and an honest list of what was not checked.</td>
  36. </tr>
  37. <tr>
  38. <td valign="top"><b>Know what is live</b><br>See every copy of the code, on your laptop, GitHub and the cloud, and which are out of date.</td>
  39. <td valign="top"><b>Keep context between sessions</b><br>Decisions, meetings and progress live in a private vault that any session can pick up.</td>
  40. <td valign="top"><b>Keep client data private</b><br>Names, quotes and figures stay in the vault, out of repos, PRs and outside services.</td>
  41. </tr>
  42. </table>
  43. ## Quick start
  44. In Claude Code:
  45. ```text
  46. /plugin marketplace add BrandeisPatrick/fde-stack
  47. ```
  48. ```text
  49. /plugin install fde@fde-stack
  50. ```
  51. ```text
  52. /fde:fde progress
  53. ```
  54. This runs against a bundled [sample project](skills/fde/sample-vault/README.md), so there is nothing to set up. You can also just ask: "how far along is Contoso?"
  55. To use it on your own work, run `/fde:fde initialize` once per project.
  56. <details>
  57. <summary>Install without the plugin</summary>
  58. ```bash
  59. git clone https://github.com/BrandeisPatrick/fde-stack ~/code/fde-stack
  60. ```
  61. ```bash
  62. mkdir -p ~/.claude/skills && ln -s ~/code/fde-stack/skills/fde ~/.claude/skills/fde
  63. ```
  64. The command is then `/fde` instead of `/fde:fde`. Update with `git -C ~/code/fde-stack pull`.
  65. </details>
  66. ## See it work
  67. `/fde` at the start of a session. One message, and every line links to the note behind it:
  68. ![Claude Code reply to /fde: a one-line priority, then status, what changed, progress bars and the user's actions.](docs/assets/screens/fde.svg)
  69. <table>
  70. <tr>
  71. <td width="50%" valign="top"><img src="docs/assets/screens/fde-architecture.svg" alt="Claude Code reply to /fde architecture: local copies, GitHub and the live deployment, each with its version."></td>
  72. <td width="50%" valign="top"><img src="docs/assets/screens/fde-initialize.svg" alt="Claude Code reply to /fde initialize: a ten-row checklist and the login command to run."></td>
  73. </tr>
  74. <tr>
  75. <td align="center"><code>/fde architecture</code> · what runs where</td>
  76. <td align="center"><code>/fde initialize</code> · is everything ready</td>
  77. </tr>
  78. </table>
  79. All examples use Contoso, a made-up company.
  80. ## How it works
  81. ![A session in five parts: start, work, ship and close in a row, the story page under work and ship, and the private vault under all of it.](docs/assets/how-it-works.svg)
  82. | Part | What happens |
  83. |---|---|
  84. | **1&nbsp;·&nbsp;Start** | Reads the vault, checks the code, deployment and logins, then sends one status message. Questions follow one at a time. |
  85. | **2&nbsp;·&nbsp;Work** | The main session orchestrates while agents build, each in its own worktree. |
  86. | **3&nbsp;·&nbsp;Ship** | Branches are integrated, a PR opens with diagrams, and the build deploys. |
  87. | **4&nbsp;·&nbsp;Story** | A private page shows the build as it happens, ready to share. |
  88. | **5&nbsp;·&nbsp;Close** | Decisions and progress are written back to the vault. |
  89. Skip what does not apply. A ten-minute fix needs part 1 and a PR.
  90. ### The agent team
  91. ![An Opus orchestrator above six agents: scout, platform, feature, integrator, reviewer and QA, with the story agent below.](docs/assets/agent-team.svg)
  92. | Agent | What it does | Works in |
  93. |---|---|---|
  94. | Scout | Maps the code and the cloud project before anything is built | Read-only |
  95. | Platform | Builds cloud infrastructure and deploys | Its own worktree |
  96. | Feature | Builds one feature, with its tests | Its own worktree |
  97. | Integrator | Merges the agent branches, runs the full tests, keeps the PR current | The integration branch |
  98. | Reviewer | Reviews correctness and security before each deploy | Read-only |
  99. | QA | Red-teams and checks the deployed build | Read-only |
  100. | Story | Turns the run log and git history into the story page | The vault |
  101. ### The vault
  102. A private Git repo with one folder per project. `/fde initialize` creates it.
  103. ```text
  104. vault/
  105. ├── platforms/ defaults shared by every project
  106. └── <project>/
  107. ├── project.md facts: code, deployment, access, people, workstreams
  108. ├── timeline.md meetings and decisions, newest first
  109. ├── meetings/ condensed notes, one file per meeting
  110. └── story/ story page source and run log
  111. ```
  112. ## Commands
  113. | Command | What it does | |
  114. |---|---|---|
  115. | `/fde` | Catch up on a project in one message | [example](docs/assets/screens/fde.svg) |
  116. | `/fde initialize` | Set up a project and check it is ready | [example](docs/assets/screens/fde-initialize.svg) |
  117. | `/fde progress` | One bar per workstream | [example](docs/assets/screens/fde-progress.svg) |
  118. | `/fde timeline` | What happened, day by day | [example](docs/assets/screens/fde-timeline.svg) |
  119. | `/fde context` | The project's facts | [example](docs/assets/screens/fde-context.svg) |
  120. | `/fde project` | Every project in your vault | [example](docs/assets/screens/fde-project.svg) |
  121. | `/fde architecture` | What runs where, and what is out of date | [example](docs/assets/screens/fde-architecture.svg) |
  122. | `/fde visual` | Redraw a reply as a diagram | [example](docs/assets/screens/fde-visual.svg) |
  123. | `/fde recap` | Cut a reply to a few lines | [example](docs/assets/screens/fde-recap.svg) |
  124. With the plugin, each command is prefixed: `/fde:fde progress`.
  125. ## Requirements
  126. - Claude Code
  127. - GitHub CLI (`gh`), signed in
  128. - `gcloud` or `aws`, if the project deploys there
  129. - A private GitHub repo for the vault; `/fde initialize` can create it
  130. ## Data handling
  131. <table>
  132. <tr><td><b>Reads</b></td><td>Project repos, deployment state (read-only), meeting transcripts, and Teams and email if you enable them</td></tr>
  133. <tr><td><b>Stores</b></td><td>Notes and transcripts, only in your private vault</td></tr>
  134. <tr><td><b>Never</b></td><td>Puts client names, meeting quotes or commercial figures in repos, PRs or outside services. Never stores keys or tokens</td></tr>
  135. <tr><td nowrap><b>Asks first</b></td><td>Before deleting work, merging a PR or enabling GitHub Pages</td></tr>
  136. </table>
  137. ## FAQ
  138. <details>
  139. <summary>Do I need GCP or AWS?</summary>
  140. No. Cloud checks are skipped for a project with no deployment.
  141. </details>
  142. <details>
  143. <summary>Does it work in the terminal?</summary>
  144. Yes. The desktop app shows questions as buttons and draws diagrams inline. The terminal uses plain text and tables.
  145. </details>
  146. <details>
  147. <summary>Do I need a GitHub repo for the vault?</summary>
  148. No. A local folder works, and nothing is pushed.
  149. </details>
  150. <details>
  151. <summary>Where do meeting transcripts go?</summary>
  152. Only into your vault. Full transcripts are kept only when the vault is private and readable by you alone; otherwise the skill keeps condensed notes and a link.
  153. </details>
  154. <details>
  155. <summary>Is the sample data real?</summary>
  156. No. Contoso, Fabrikam and Northwind are made up.
  157. </details>
  158. ## Contributing
  159. Issues and pull requests are welcome. [CLAUDE.md](CLAUDE.md) has the repo's rules and the checks to run.
  160. ## License
  161. MIT · [Full skill text](skills/fde/SKILL.md) · [Changelog](CHANGELOG.md)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.