Projects
Projects are the top-level containers in DevFlow. Every Flow, release, time entry, and team assignment lives inside a project. Whether you are building a single product or managing several, each project gives you a dedicated workspace with its own Kanban board, dashboard, and settings.
Creating a Project
Section titled “Creating a Project”- Click “New Project” in the sidebar or on the Dashboard
- Enter a project name
- Optionally add a description, logo, and color
- Click Create
Your project appears in the sidebar immediately. You are redirected to the project settings page where you can configure details.
Project Settings
Section titled “Project Settings”Open settings via the gear icon on the project page. Settings are organized into five tabs.
General
Section titled “General”- Project Name and Description — Identify your project. Changes save automatically as you type.
- Flow Prefix — A 2-5 character code used for Flow IDs. For example, if the prefix is
MA, Flows are numberedMA-1,MA-2, and so on. DevFlow auto-suggests a prefix based on the project name. - Color — Pick a color to visually distinguish this project in the sidebar, timer, and time tracking views.
- Logo — Upload an image (PNG, JPG, or SVG, max 500 KB) or paste an image URL. The logo appears in the sidebar and on project cards.
- Auto Timer — When enabled, the timer automatically starts and switches context when you begin working on Flows in this project.
- Tracking Level — Choose what granularity time is tracked at: Project, Flow, or Ticket.
- Takt (Rounding) — Set a project-specific rounding interval for time blocks (5, 15, 30, or 60 minutes). Leave empty to use your global default.
- Transfer Project — Owners can move a project between their personal space and an organization.
- Delete Project — Permanently removes the project. Only available to the project owner.
If your project belongs to an organization, the Team tab shows all members and their roles. You can manage who has access and what permissions they hold.
For personal projects (outside an organization), you are the only member.
Knowledge
Section titled “Knowledge”Store project-specific documentation, architecture notes, tech stack details, and agent instructions. This information is available to AI agents working on the project, helping them understand your codebase and conventions.
The Rules tab configures two things: Pipeline Rules (how agent and human collaborate) and Git Workflow (branch/commit/PR conventions).
Pipeline Rules
Section titled “Pipeline Rules”The pipeline defines what happens at each step of a Flow — from idea to done. Each step is shown as a card with a header indicating the Flow state it belongs to (matching the Kanban columns).
Presets — Start with a preset and customize from there:
| Preset | Description |
|---|---|
| Off | Minimal process — only the execution step is active, agent runs freely |
| Balanced | Standard workflow — agent plans, human approves, agent implements, human tests |
| Strict | Maximum control — all steps active, reviews at every stage |
| Custom | Shown when you have manually adjusted any step |
Pipeline Steps — Each step has an actor setting that controls who does the work:
| Actor | Meaning |
|---|---|
| Human | Only the human works in this step |
| Agent | Only the AI agent works in this step |
| Both | Either human or agent can work |
| Auto | System step, no active worker (e.g., Ready, Done) |
| Skip | Step is skipped entirely |
Click the actor badge on a step card to cycle through the options.
How steps relate to the Kanban board:
The pipeline steps map to Flow states (the columns on your Kanban board). Most states have one step, but review contains two sub-steps:
| Kanban Column | Pipeline Step(s) |
|---|---|
| Idea | Idea |
| Planning | Planning |
| Approval | Approval |
| Ready | Ready |
| In Progress | Execution |
| Review | Review → Testing |
| Done | Done |
Gate behavior — Steps with specific transition policies control who can move a Flow forward:
- Approval and Testing are gate steps — the AI agent is blocked until a human approves or rejects in the DevFlow UI
- Idea, Planning, Execution, Review — both agent and human can advance the Flow
- Ready and Done — automatic system transitions
Skills — Agent steps can have skills assigned across three phases:
- Pre — Preparation before the main work (e.g., brainstorming, branch creation)
- Action — The main work (e.g., writing plans, implementing code)
- After — Follow-up work (e.g., design docs, commit & PR)
Click the phase dots below a step card to assign or change skills.
Reject loops — When a human rejects work at a review step (Approval or Testing), the Flow goes back to a previous step. The info box below the pipeline shows these reject paths (e.g., “On reject: Approval → Planning”).
Git Workflow
Section titled “Git Workflow”Toggle Git workflow on/off. When enabled, configure:
- Branch Convention — How Flow branches should be named (e.g.,
feature/MA-1-add-login) - Commit Convention — Commit message format (e.g., conventional commits)
- PR Template — How pull request descriptions should be structured
Click the edit icon on each convention to customize. A live preview at the bottom of the page (“What the agent sees”) shows how the generated guidelines will look to the AI agent.
Strictness Levels
Section titled “Strictness Levels”The overall enforcement level (shown in the preview as “Paranoid”, “Standard”, etc.) is configured per-project and affects how strictly the agent must follow the rules. Higher levels require more documentation, planning, and review steps.
Extensions
Section titled “Extensions”Connect external tools to your project. Integrations (GitHub, GitLab, Slack) are planned for future releases.
Project Dashboard
Section titled “Project Dashboard”Each project has a dedicated dashboard that gives you an overview of the current state:
- Flow Pipeline — A visual summary of how many Flows are in each state (idea, planning, approval, ready, in progress, review, done)
- Recent Activity — The latest Flow updates, state transitions, and team actions
- Release Progress — Status of the current active release, including how many Flows are completed vs. remaining
- Time Statistics — Hours tracked per week and month, broken down by project member
Project Permissions
Section titled “Project Permissions”Projects support three roles with different access levels:
| Role | Capabilities |
|---|---|
| Owner | Full control. Can edit all settings, transfer or delete the project, manage members and roles |
| Manager | Can edit project settings, manage Flows, and manage team members |
| Member | Can view the project, create and work on Flows, and track time |
In organization-owned projects, roles are inherited from the organization membership but can be adjusted at the project level.