Product tour
A look inside Penling
A walkthrough of the Penling workflow — what it looks like when you're actually using it.
Step 1 · The brief
Turn a rough idea into a structured brief
Use the brief creator to describe what you're building — the goal, key deliverables, constraints, and anything that's explicitly out of scope. This becomes the shared source of intent that everything downstream is derived from.
Step 2 · Goals
Identify goals and focus areas from your brief
The goals generator reads your brief and proposes the logical goals and focus areas that follow from it. Review what it surfaces, adjust where needed, and confirm before moving forward — the brief does the heavy lifting, you stay in control of what gets built.
Step 3 · Overview
See your project taking shape
The overview screen gives you a snapshot of the whole initiative — health, progress, and what needs attention next. Come back to it at any point in the workflow to reorient, or to hand context to someone else joining the project.
Step 4 · Focus areas
Define and plan your focus areas
Break the project into logical units of grouped work and plan each one out ready for the build stage. Attach context files — existing code, designs, reference docs — so the agent has everything it needs before it touches a single line.
Step 5 · Build list
Queue up tasks ready for your agent
Once your plan is activated, tasks are queued and ready to be claimed by your LLM. Each one is fully specified — the agent knows what to build, what to leave alone, and what done looks like before it starts.
Step 6 · Build
Claim the build and work it with your agent
Once the build is claimed via the Penling MCP, hand it to the LLM of your choice and work through it. Results come back verified, PR'd, and specified — the full chain of reasoning attached and on the record.
Step 7 · Canvas
Watch the work unfold in real time
Everything is streamed live to the canvas as the agent works — your whole team can watch it happen. It's also a permanent visual record of exactly what took place, in what order, when the work was done.
Step 8 · Pull request
A PR your team can actually review
Penling submits the PR with all acceptance criteria met and tests passing. The specification is attached — reviewers can see not just what changed, but why it was built that way and what it was built against.
Step 9 · Documentation
Keep everything under one roof
Use the Penling documentation system to record build diaries, new findings, team notes, or anything else worth keeping. It lives alongside your work, so nothing gets lost in a separate tool — and everything stays discoverable by the people who need it.