Agent skill · Workflow & Productivity

existing-solution-map

description: Produce existingsolutionmap.md to ground task generation in the current repo.'

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill existing-solution-map --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 5 KB
Bundled scripts: none
Path: skills/analysis/existing-solution-map/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

--- description: Produce existing_solution_map.md to ground task generation in the current repo. argument-hint: "<IDEA_ID> [--epic EPIC-00X]" --- # Existing Solution Map — Agent Instructions ## Invocation - `/existing-solution-map <IDEA_ID> [--epic EPIC-00X]` Where: - `IDEA_REF = $ARGUMENTS` (single token; no spaces) - Optional `--epic EPIC-00X` narrows the map to one epic’s features. If missing, STOP. --- ## Resolve IDEA_ID (required) Before using any paths: - Call `vf.resolve_idea_id` with `idea_ref = $ARGUMENTS` - Store returned `idea_id` as `IDEA_ID` --- ## Goal Create an actionable map of “what already exists” in the repo for this idea (or for one epic), so that downstream task generation can be extension-oriented and avoid duplicate subsystems. This artifact is treated as a required input for task generation. --- ## Canonical paths (repo-relative) Inputs (required): - `docs/forge/ideas/<IDEA_ID>/latest/concept_summary.md` - `docs/forge/ideas/<IDEA_ID>/latest/features_backlog.md` (preferred) or `latest/features.md` (fallback) Optional inputs: - `docs/forge/ideas/<IDEA_ID>/latest/epics_backlog.md` (to resolve epic→feature grouping) - `docs/forge/ideas/<IDEA_ID>/latest

What's inside
Steps it walks through
  1. Invocation
  2. Resolve IDEAID (required)
  3. Goal
  4. Canonical paths (repo-relative)
  5. Method (generic, reuse-first)
  6. Output format: existingsolutionmap.md
  7. Scope
  8. Existing “happy path” flow (as implemented today)
  9. Reuse-first decisions (hard rules)
  10. Key extension points (by capability area)
  11. API/endpoint layer
  12. Core logic / domain layer
  13. Models / state / schemas
  14. UI layer
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the existing-solution-map skill do?

description: Produce existingsolutionmap.md to ground task generation in the current repo.'

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill existing-solution-map --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going