Glossary

Terms used throughout the Ideafy docs and interface. Alphabetical.

Autonomous

A processingType value. When autonomous is running on a card, the agent detects the phase (plan / implement / test) and drives the card through the workflow without interactive prompts.

Branch enforcement

A policy enforced by the PreToolUse hook plus the ensure_branch MCP tool. When a session is bound to an In Progress card and the card (or its project) has worktrees enabled, Claude is blocked from calling Edit / Write / NotebookEdit / MultiEdit while the working tree is on the wrong branch. The deny message instructs Claude to call ensure_branch, which creates or switches to the correct branch, after which the edit succeeds on retry. See Bundled Claude Code hooks.

Card

The primary unit in Ideafy. A container with title, description, plan (Solution), tests, AI opinion, git metadata, conversation history, and more. Lives in one of the seven kanban columns.

Claim

A pool operation. Self-assigns an unassigned pool card to you without pulling it into your local board. Admins / owners can also claim a card away from someone else; regular members can only claim from null. Claim doesn't create a local copy — for that you need Pull. Paired with Unclaim.

Claude Code plugin

Ideafy's integration shipped as a native Claude Code plugin — a single package bundling the MCP server, phase-aware hooks, and the ideafy:ideafy-workflow skill. Distributed via the marketplace at github.com/ozangencer/ideafy-claude-plugin. Installable from the Ideafy UI (Settings → General for user scope, Edit Project for project scope) or from Claude Code directly with /plugin install ideafy@ideafy. See Claude Code plugin.

Completed

The sixth kanban column. Cards with a set completedAt live here. The column has a date filter (Today / Yesterday / This Week / All).

Conversations

Per-section chat threads in the card modal. Stored in the local SQLite conversations table, scoped by (cardId, sectionType). Never synced to the cloud. Backed by a CLI session ID (see Interactive CLI sessions) that resumes via claude --resume <id> on every follow-up message, so threads stay alive across days.

Chat triggers

Three characters that open autocomplete menus in the card chat input: @ for documents, `Card chat & mentions.

Display ID

The {prefix}-{taskNumber} identifier shown on card surfaces (e.g., KAN-14). The prefix comes from the project; the task number is assigned incrementally per project.

Document Paths

A per-project list of extra files or folders the sidebar Documents section should surface. Set under Project settings → Document paths. Not an override: your paths render at the top in user-defined order, and smart discovery fills the rest below a divider. See Project settings.

Evaluate

A processingType value. Runs only on Ideation cards. Loads the Product Narrative as context, produces an AI opinion with a verdict (positive / negative). Uses save_opinion.

Fire-and-forget sync

The mechanism Ideafy uses to keep pool cards in sync. Every local card mutation fires a POST /api/internal/sync-card call. Failures are silent; the next mutation retries.

Grace period

5-day window after trial expiry, payment failure, or cancellation. Pool writes are blocked but reads still work. After grace, the subscription is expired.

Hook

A .claude/settings.json shell command that runs at a specific agent lifecycle point. Ideafy installs two: a UserPromptSubmit hook that returns phase-aware policy, creation offers, and offline reminders; and a PreToolUse hook that blocks edits landing on the wrong branch while bound to an in-progress card. Both fail open if the Ideafy server is unreachable. See Bundled Claude Code hooks.

Human Test

The fifth kanban column. A card lives here when implementation is done and a human needs to verify acceptance criteria — typically by ticking off the Tests tab checkboxes. Designed so a non-developer (product owner, business analyst, founder) can drive a card from here to Completed using the Tests-tab chat panel, including committing and pushing fixes via --dangerously-skip-permissions.

Ideation

The first kanban column. Raw ideas and rough notes go here before being scoped into the Backlog.

Invite code

A 6-character alphanumeric string used to join a team. Generated once at team creation, doesn't rotate, doesn't expire.

Marketplace (Claude Code)

A git repo with a .claude-plugin/marketplace.json at its root that declares one or more plugins. Claude Code's plugin CLI clones the marketplace into ~/.claude/plugins/marketplaces/<name>/ and installs plugins from marketplaces/<name>/plugins/<plugin>/ into ~/.claude/plugins/cache/<name>/<plugin>/<version>/. Ideafy's marketplace lives at github.com/ozangencer/ideafy-claude-plugin.

MCP (Model Context Protocol)

Anthropic's protocol for exposing tools to AI agents. Ideafy ships its own MCP server that exposes 15 tools for card management. On Claude Code it's delivered via the Claude Code plugin; on Codex / Gemini it's installed through the classic project toggle.

Memory (Claude auto-memory)

The per-project notes Claude Code writes to itself across sessions. Files live at ~/.claude/projects/<dash-encoded-folder>/memory/, with MEMORY.md as the index. Ideafy surfaces them as a dedicated Memory section in the sidebar (when the active AI platform is Claude) and makes them @-mentionable in card chat. Memory files are Claude's, not Ideafy's — Ideafy only reads and references them. See Card chat & mentions.

My Queue

A UI view showing pool cards assigned to you that you haven't pulled locally yet. Your personal inbox inside the pool.

Narrative (Product Narrative)

A markdown document at docs/product-narrative.md (or configured path) that describes the project's vision, problem, target users, features, non-goals, tech stack, and success metrics. Loaded as context for every evaluate run.

Plugin scope

How a Claude Code plugin is activated. User scope enables the plugin in every project on this machine — flag lives in ~/.claude/settings.json → enabledPlugins. Project scope enables the plugin only when a specific project is active — flag lives in <project>/.claude/settings.json → enabledPlugins. Both scopes can coexist for the same plugin; the project dialog shows an Inherited badge instead of a toggle when user scope already covers the project. See Claude Code plugin.

Pool

The shared Supabase table where team members push cards and pull them back. Exists only in the Team edition.

Pool origin

A local card field: pushed / pulled / null. Tells you how this local row came to be linked to its pool card — you pushed it from your board (pushed) or you created it by pulling a pool row (pulled). Drives the badge shown in My Queue and the trigger condition for the release dialog.

Processing type

A card state: autonomous / quick-fix / evaluate / null. Non-null values indicate a background agent job is running on the card. While set, the card is locked in the UI.

Pull (pool)

A pool operation. Atomically claims a pool card and creates a new local card on your machine with poolOrigin = "pulled". Only one puller wins per card. Sets pulled_by = you and assigned_to = you on the pool row (the pull lock).

Pull lock

Informal name for the pool_cards.pulled_by field. Identifies whoever currently holds the active local copy of a pool card. Ideafy auto-manages it: set on pull, also set on self-claim push (since the pusher already has the local), cleared when the holder unpulls, deletes their local, or runs the release dialog. At most one team member holds the lock at a time, so a second member can't pull a card that's already been pulled — they see a 409. See pool mechanics.

Push (pool)

A pool operation. Copies a local card into the team's Supabase pool. Your local copy stays; the pool copy becomes the shared state. If you push with assigned_to = yourself (self-claimed push), the pool row is also marked with your name in the pull lock — you already hold the local, so that lock belongs to you from the start.

Push update

Re-syncing a pool-linked local card's content back to the pool row. Authorized for the holder of the pull lock OR the original pusher while pulled_by is still null. Driven by the Update Pool button in the card modal and by auto-sync on drag-drop status moves.

Quick-fix

A processingType value for the Bugs column. Short, targeted fix without plan/test ceremony. Doesn't move the card's status.

Reassign (pool)

Changing a pool card's assigned_to from one member to another (or to null). Allowed for the current assignee and for admins / owners — members can hand off their own work without needing admin mediation. If the reassigner holds the pull lock and the new assignee is a different person, the release dialog kicks in to keep local and pool in sync.

Release dialog

A shadcn AlertDialog that fires in the card modal when the puller of a pool card changes Assignee to Unassigned or to another teammate. Confirms a three-step atomic release: (1) push any unsaved local edits back to the pool, (2) apply the unclaim / reassign on the pool row, (3) delete the local copy and clear the pull lock. Cancelling reverts the Assignee dropdown. See pool mechanics.

Seat

One team member. Billing is per-seat. Trial is capped at 5 seats; paid plans set seats at checkout and enforce them at join time.

Skill

A markdown file loaded by Claude Code (or platform equivalent) that instructs the agent how to handle specific tasks. Ideafy ships three classic skills — ideafy.md, human-test.md, product-narrative.md — installed into .claude/skills/ (or ~/.codex/skills/, ~/.gemini/skills/) by the Ideafy MCP & Skills toggle. The Claude Code plugin additionally ships ideafy:ideafy-workflow, a namespaced plugin-sourced skill read directly from the plugin cache. Skills can be organized into skill groups in the sidebar.

Skill group

A user-named collection of skills that appears as a collapsible header in the sidebar Skills list. Groups are purely organizational — they don't move files on disk and don't change how the agent loads a skill. Each group has a scope (global for all projects, project for the active one) and is persisted in the local SQLite database. Groups also show up as expandable entries in the / menu in card chat. Managed via the Organize toggle at the top of the Skills sidebar section. See Bundled Claude Code skills.

Smart discovery

The automatic walk Ideafy performs against every project folder to populate the sidebar Documents tree and the @ mention popup. Covers a curated list of directories (docs, documentation, wiki, notes, specs, design, architecture, adr, plans, .github) up to three levels deep, plus important root files (CLAUDE.md, README.md, CONTRIBUTING.md, CHANGELOG.md, ARCHITECTURE.md, SECURITY.md, LICENSE.md). Runs on every documents fetch, with or without user-supplied Document Paths. Skips node_modules, dist, build, .git, .next, coverage, __pycache__, and venv / .venv.

Solo mode

The fallback when no auth is configured. Full local functionality, no team features. Default for Public edition; the Team edition falls back to it automatically when Supabase env vars are missing.

Sync-card

The fire-and-forget sync endpoint (POST /api/internal/sync-card) that propagates local card mutations to Supabase pool cards.

Task number

The numeric part of a card's display ID. Assigned incrementally per project from projects.nextTaskNumber.

Unclaim

A pool operation. Clears the current assignee on a pool card. Allowed for the current assignee (unclaim your own) and for admins / owners (unclaim someone else's). If you unclaim while holding the pull lock on a pulled card, the modal runs the release dialog to also drop the local copy — otherwise the card can't be pulled by anyone else until you free the lock.

Unpull

The companion to Pull. Clearing the pull lock so another member can pull the card. Triggered automatically when you delete a local pool-linked card (with removeFromPool = false) — the client calls /api/team/pool/unpull before the delete.

Verdict

The aiVerdict field on a card: positive / negative / null. Set by save_opinion. Shown on the card surface as a Brain icon with a checkmark or cross.

Voice

Project-level tone setting that drives prose style across every AI surface — plan, tests, opinion, chat, autonomous flows, and solution summaries. Three personas: entrepreneur (plain product prose), builder (default; plain technical), engineer (spec-style with file:line). Voice changes only tone — technical content is preserved across all three. Each AI surface layers a section-specific accent on top of the base persona. Set per project in Project settings → Voice.

Withdrawn

The seventh (terminal) kanban column. Cards you decided not to ship are archived here. A negative verdict plus a Withdrawn move is a clean audit trail for "why we said no."

Worktree

A git worktree — an isolated checkout of the repository tied to a branch. Ideafy creates one per card in implementation, at .worktrees/kanban/[PRJ-N-...].

Prev: FAQ Next: Keyboard shortcuts Up: User guide index