Start simple
A shared board. A clear next step.
Pencil brings Claude and OpenAI models into a shared product workspace. Keep requirements, features, decisions, and delivery history connected, so your team and agents can build on what you already know.
| Task | Status | Priority | Assignee / Agent |
|---|---|---|---|
| In Progress | high | ◎ You ▣ Dabi | |
| blocked | medium | ◎ Sam ▣ Nova | |
| Review | medium | ◎ You ▣ Aria | |
| Done | low | ◎ Sam ▣ Nova | |
| Done | high | ◎ You ▣ Dabi | |
| Done | high | ◎ Jules ▣ Dabi | |
| Done | high | ◎ Sam ▣ Dabi | |
| Done | medium | ◎ Lee | |
| Done | medium | ◎ Lee | |
| In Progress | medium | ◎ Jules ▣ Nova | |
| Inbox | medium | ◎ Lee | |
| backlog | low | ◎ Jules ▣ Aria |
Expand the sprint summary, switch layouts, or explore the menu. All data is fictional and interactions stay in this preview. Pencil’s default dark theme is shown; navigation and fields are configurable in your workspace.
Claude, ChatGPT, and other AI assistants are useful places to think, write, and build. Pencil adds a structured home for the product work around those conversations: what you need, why it matters, who owns it, and what happened next.
Pencil can use Claude from Anthropic and GPT models from OpenAI, the company behind ChatGPT. You get the capabilities of the model you choose, with Pencil organizing the context and workflow around it. Available models and billing depend on your setup.
| The work | AI chat on its own | What Pencil adds |
|---|---|---|
| Product needs | Describe the feature and supply its background in your conversation. | Track ideas, requirements, and features as shared product records. |
| Decisions + history | Bring the relevant prior discussions and decisions into the work. | Keep decisions, comments, files, and memories accessible alongside the work. |
| Team handoffs | Share the conversation and explain who should do what next. | Give tasks human and agent owners, priorities, status, and review requirements. |
| From plan to delivery | Carry the result into your planning and delivery tools. | Connect product plans to tasks, agent outputs, GitHub work, and deployments. |
| Visibility | Review the answer or generated code in the conversation. | Inspect task progress, outputs, and usage by agent, model, project, and task. |
AI assistants may also offer memory, projects, and integrations. This comparison describes workflows; Pencil’s focus is a shared, structured product record across people, agents, and tools.
Use Pencil directly, or access it from Claude through Pencil’s MCP server. Add the Pencil skill to give Claude your workflow instructions, then ask it to read the relevant requirements and decisions before it builds.
You, in Claude
“Build team invitations. First, check Pencil for the requirements and decisions we’ve made about this feature. Use that context in the implementation, flag anything unresolved, and save a summary of the work back to the task.”
Requirement: admins can invite teammates by email.
Decision: invitations expire after seven days.
Open question: can guests invite other guests?
Use the invitation rules in the implementation. Ask for a decision on guest permissions before expanding the scope.
Record the implementation summary, test results, and remaining questions on the Pencil task.
Illustrative example. Claude needs authorized MCP access and development tools to implement code; the skill alone does not connect your workspace.
Assign a person and an agent to the same task. Keep responsibility visible as work moves across the board.
Follow progress, inspect outputs, and review agent contributions in the context of the task.
Keep decisions, files, and agent memory connected to the work they inform.
Start with shared tasks, clear owners, and collaboration. Turn on more tools when your team needs them—not before.
A shared board. A clear next step.
Bring in the tools that fit your work.
Expand when your team is ready.
Pencil keeps status, priority, human assignment, and agent assignment with the task. Open a card to inspect the brief and the work behind it.
Use checklists and agent outputs to understand what’s ready. Configure plan approval and review requirements for the work that needs them.
Keep the welcome flow focused: introduce the workspace, find a first task, and make the next step clear.
Example output: onboarding-copy.md
Saved against this task for review.
Browse an agent’s memories and files side by side. Keep facts, decisions, and lessons accessible, and inspect the context your agents use.
Agent memories · MEMORY.md · lessons.mdKeep onboarding to three steps.
onboarding · 2h agoThe launch brief is attached to MC-129.
launch · 1h ago# Project context Keep onboarding short. Link work to its brief. ## Next Review the launch copy.
Sample agent memories and files. No live workspace connection.
Track usage by agent, model, project, and task. Pencil separates equivalent token usage from billed spend, so flat-rate and local runs don’t disappear from the picture.
Usage trends · Cost breakdowns · Model routingIllustrative data · Equivalent usage can differ from billed spend.
Bring conversations, documents, and code into the same workspace.
Connect external AI clients through hosted MCP or a paired local gateway. Use the REST API for custom tools and structured integrations.