repository-feature-plan

Plans how a new feature fits into an existing repository's architecture, tests, and documentation.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/vmitsaras/Agent-Skills --skill repository-feature-plan-vmitsaras
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repository-feature-plan
Source: https://github.com/vmitsaras/Agent-Skills/tree/main/skills/project-planning/repository-feature-plan
Command: npx skills add https://github.com/vmitsaras/Agent-Skills --skill repository-feature-plan-vmitsaras

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Adding a feature to an unfamiliar or large codebase often leads to architectural drift, duplicated abstractions, and missed test or documentation updates. This Skill inspects the actual repository and produces a concrete, repository-aware implementation plan before any code is written. ## Core Features & Use Cases - Architecture Mapping: Locates relevant entry points, modules, routes, and data flows, then identifies which existing abstractions to extend rather than duplicate. - Convention Discovery: Detects naming, folder organization, testing, styling, and documentation patterns from existing code so the plan mirrors project conventions. - Full-Surface Planning: Produces an ordered implementation plan covering code changes, unit/integration/e2e tests, docs, examples, demo updates, risks, and a handoff checklist. - Use Case: A maintainer asks where a new export feature should live in a monorepo. The Skill inspects the target package, cites the files that shaped its reasoning, and returns a step-by-step plan a coding agent can implement safely. ## Quick Start Ask the agent to plan how your proposed feature fits into this repository, including which files will change and how to update tests, docs, and demos.

Frequently Asked Questions about repository-feature-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan a new feature for an existing codebase?▼

Start by defining the feature boundary, then inspect the repository's architecture, conventions, and tests before writing code. This Skill automates that inspection and returns an ordered implementation plan with likely files to change, test strategy, and documentation updates.

How to decide where a feature belongs in a repository?▼

Locate existing modules near the feature area, identify abstractions worth extending, and check ownership boundaries between layers. The Skill maps entry points, routes, and data flows, then recommends a location justified by patterns found in the actual code.

Does this feature planning skill work with monorepos?▼

Yes. For repositories with multiple apps, packages, or workspaces, it first identifies the target package and shared boundaries before planning any file changes, so cross-package coupling is avoided.

Can it write the implementation code after planning?▼

No. It deliberately avoids code patches, diffs, and implementation snippets. The output is a planning artifact with a handoff checklist designed for a coding agent or maintainer to implement separately.

What if the repository has no tests or documentation?▼

The Skill proposes the smallest test scaffold matching the repository's existing tooling rather than prescribing a new stack, and recommends whether minimal docs or demo additions are necessary for the feature.