• 3 min read
Claude Code gets a file-based workflow for product managers
A public Claude Code workspace turns product work into persistent files, reusable skills, and repeatable workflows instead of disposable chat threads.
Source: Hacker News
Claude Code can be useful for product work even when the workspace contains almost no code. The approach described by [Hacker News](https://www.theaithinker.com/p/how-to-organize-claude-code-for-product) treats the tool as a file-based work system: persistent company context, separate project folders, reusable skills, and saved feedback that does not need to be repeated in every session.
The central idea is simple: prompts improve one session, while well-organized files improve every session after it. Chat is good for thinking, but conversations often leave strategy documents, corrections, and useful outputs buried in threads. Claude Code instead works inside a folder it can read, navigate, and update.
The public GitHub starter workspace, claude-code-pm-starter, packages this structure into a template. It includes guided context files, an example project, five installed skills, and folders for projects and operations. The setup is designed for product managers, but the same pattern can support other context-heavy jobs, including design research, data definitions, and founder workflows.
The workspace is built around a few persistent areas:
- Context: company, product, users, competitors, and working preferences.
- Projects: active work, with tasks kept separate from deliverables.
- Operations: dated notes and recurring work.
- Skills: repeatable tasks such as status updates, PRD reviews, and interview synthesis.
- CLAUDE.md: a map explaining where information lives and which rules apply in each session.
That organization also creates a feedback loop. Corrections can be written to a file with a note explaining why they were made, so the same feedback does not have to be supplied repeatedly.
Setting up the Claude Code workspace
The starter requires a paid Claude plan. The other two tools in the setup are free: Claude Code and VS Code. VS Code serves primarily as a visual file browser; users do not need to write code in it.
Download the starter repository as a ZIP from GitHub, unzip it, and place it in a permanent work folder. No Git installation or GitHub account is required for this route.
Open the folder in VS Code, then create a terminal inside the editor. Moving the terminal panel to the right leaves the file tree on the left and Claude Code beside it, making the workspace easier to understand than a standalone command line.
After installing Claude Code from Anthropic’s official guide, run claude in that terminal. Claude Code starts in the workspace, reads the map file, and can use the folder structure from the first interaction.
The distinction between the terminal and Claude Code matters for new users: the terminal requires exact commands, while Claude accepts normal-language requests once it is running.
Useful commands include:
- /model to view or switch models.
- /effort to control how much reasoning Claude applies.
- /mcp to manage connections to tools such as Jira, Slack, or Confluence.
- /plugins to browse and manage plugins.
The default Anthropic marketplace includes 276 plugins, according to the workspace walkthrough. One product-management option, pm-skills, contains more than 100 skills spanning discovery, strategy, execution, and launch. The guide recommends installing only the skills that match the work, since every installed plugin adds context the system carries.
Claude Code also has three operating modes, switched with Shift+Tab:
- Default: asks for permission before changing files.
- Auto-accept: applies edits without asking.
- Plan: researches and proposes a plan without changing anything until approval.
The recommended starting point is Default mode, with Plan mode for larger tasks and Auto-accept reserved for workflows the user already trusts.
The practical payoff is not a more elaborate prompt. It is a workspace where company knowledge, active tasks, reusable procedures, and prior corrections remain available across sessions. That makes this approach closely related to the shared rules and evaluation workflows for coding agents, although the starter workspace is aimed at product work rather than general engineering teams.
Computing Editor
Tomas lives in the terminal. He covers chips, laptops, and operating systems with a focus on performance and efficiency. He reads kernel changelogs the way other people read fiction, and he's always on the hunt for the perfect mechanical keyboard switch. If it processes data, Tomas has an opinion on it.
