Get started

How it all fits together

Productmind follows a piece of work from the moment a customer mentions a need to the release that ships it. Each step has its own page in the sidebar, and every record keeps a link to the one it came from, so you can always trace a line of code back to the customers who asked for it.

The path, step by step

StepWhereWhat happens
1. FeedbackFeedback group, Notes, the feedback widgetYou collect what customers and your team say.
2. RequestsFeature requests, Bug reportsProductmind turns feedback into feature requests and bug reports, and gathers the customers behind each one.
3. FeaturesFeaturesYou promote the requests worth building into features, and specify them.
4. TasksTasksEach feature is broken into tasks: the concrete pieces of engineering work.
5. SessionsCodeA coding session works on tasks in your repositories: it plans the change and writes the code.
6. Pull requestsInside each sessionThe session opens pull requests. Your team reviews and merges them.
7. ReleasesReleasesA release collects the merged work of your applications, and merges and tags it into production.

Your product development life-cycle on the Dashboard draws this path as cards, each with how many items are at that step: Customer feedback and Ideas, Feature requests, Work items (tasks and bug reports together), Code and Releases. Features and pull requests have no card of their own.

1. Feedback

Feedback reaches Productmind in several ways:

The people and companies behind the feedback are kept in Contacts.

2. Feature requests and bug reports

When Productmind summarizes a customer conversation, it picks out the features the customer asked for and the problems they ran into. Each feature becomes a feature request, and each problem a bug report. When a customer asks for something that already has a request, Productmind adds the customer to that request instead of creating a duplicate, so each request shows how many customers want it.

You can also create requests and bug reports yourself, and convert a note into either.

A feature request is New, In Review, then either Promoted into work, Merged into another request, or Rejected.

3. Features

Features are the capabilities of your product, organized as a tree. Promoting a request either creates a feature or adds the request to an existing one. Productmind can also discover features from the code of your applications. A feature is Backlog, Planned, In Development, Stable or Deprecated.

4. Tasks

Tasks are the engineering backlog. Most tasks sit under the feature they help build. You can add them by hand, have Productmind suggest them from a feature, promote a request straight into a task, convert a bug report, or import them from Jira or Asana.

5. Code

A session is an AI coding agent working on one or more tasks, or on a bug report, in your repositories. It can write a plan for you to approve first, then writes the code, and asks you when it needs a decision. Tasks move forward on their own as the session progresses, to In Progress, In Review and Done. See How tasks behave.

6. Pull requests

A session delivers its work as pull requests in your repository. Your team reviews them, the session answers review comments, and you merge them. When every pull request for a task is merged, the task is Done.

7. Releases

A release compares each application's development branch with its production branch to find exactly what is going out. It drafts release notes and, once the checks pass, merges and tags everything in one step. It lists the features it ships, traced back through the sessions that built them.

Lineage: following the thread

Every step above records where its work came from: a request is linked to the conversations that raised it, a feature to the requests promoted into it, a task to its feature, and a session to the tasks it worked on. Lineage, under Product, draws these links for your whole product. Most records also have a Lineage button in their header, which shows the chain for that one record.

So you can start anywhere and follow the thread in either direction: from a release back to the customers who asked for what it ships, or from a customer's request forward to the pull request that built it.

What supports the path

  • Knowledge base: documents, files and web pages that give Productmind's agents the background on your product.
  • Applications and Sandboxes: the repositories your sessions work in, and how to run them.
  • Agents and Automations: how Productmind's agents behave in your workspace, and work they do for you on a trigger or a schedule.
  • Integrations: your Git provider, issue trackers, chat and helpdesk.
Last modified on