For larger features, do not put the entire requirement only in a chat prompt; create a specification file that describes the feature in a durable form. A spec file should explain the goal, current behavior, expected behavior, functional requirements, constraints, edge cases, acceptance criteria, and important technical decisions. The spec can live in a dedicated directory such as `docs/specs/`, `specs/`, or another location defined by your project rules. Give each specification a clear name, such as `docs/specs/user-profile.md`, so developers and Claude Code can find it later. Your task prompt can then be short: ask Claude Code to read the relevant spec, inspect the repository, create a plan, and implement only what the spec requires. Keep CLAUDE.md for project-wide rules, spec files for feature requirements, and the current Claude Code prompt for the immediate action you want performed.
This separation is important because it prevents requirements from being lost in conversation history and makes the expected result easier to review. Before implementation, ask Claude Code to summarize the spec as a checklist and confirm that every acceptance criterion is understood.

The articles and images featured on this platform were generated with the assistance of AI tools.