Skip to content
Agentmart
Submit a tool

document-existing-code

Use when the user wants the requirements, spec or intended behavior of code that already exists ("what is this supposed to do", "write up the requirements for…

Skill by FMorschel

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/fmorschel-document-existing-code

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Use when the user wants the requirements, spec or intended behavior of code that already exists ("what is this supposed to do", "write up the requirements for X", "reverse-engineer a spec"). Runs the existing-feature entry: test-writer first when tests are missing, then requirements-analyst, and surfaces both agents' human-confirmation lists.

Use cases: documents, testing, writing

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/document-existing-code

What's inside

Skill name
document-existing-code
Description
Use when the user wants the requirements, spec or intended behavior of code that already exists ("what is this supposed to do", "write up the requirements for X", "reverse-engineer a spec"). Runs the existing-feature entry: test-writer first when tests are missing, then requirements-analyst, and surfaces both agents' human-confirmation lists.
License
MIT
Instructions
16 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

## Documenting existing code

The orchestrator's existing-feature entry (`Q` → `P`) without the rest of the graph. Does not edit production code.

1. **Tests present?** Yes → `requirements-analyst` alone. No → `test-writer` first, then `requirements-analyst` with the implementation **and** those tests. Order matters: the analyst needs both sources to tell a requirement from an accident.
2. Pass each agent only what its spec needs (see the orchestrator's *Context assembly*): `test-writer` gets the target implementation only.
3. Where to write the result follows `place-project-knowledge` (requirements normally go in `specs/`) and the format follows `write-requirements`. Do not invent a location silently; state where it went.
4. Optionally run `prd-architecture-consistency-checker` if the project has a PRD and `architecture.md` and the new document touches them.

### Report

The requirements document (or its path), the new tests if any, `test-writer`'s axis sweep, and both **Needs human confirmation** checklists **in full**. The user must decide whether the reconstructed intent is right before anyone treats it as ground truth; say that plainly.

Natural next steps to offer, not start: `improve-test-coverage`, `evaluate-code`, `plan-change`.

From FMorschel/agents, MIT.

More from FMorschel/agents

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Oct 18, 2026 (11 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
Repository
github.com/FMorschel/agents
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Source
GitHubgithub-graphql

More from FMorschel

Cite this page

document-existing-code skill. Agent Mart. https://agentmart.dev/skills/fmorschel-document-existing-code (last updated 2026-10-24)