Skip to main content
Pull loads a planspace into a fresh coding-agent thread as execution context. Start Claude Code, Codex, Cursor, OpenCode, Gemini, or another supported agent where you want to execute, then paste: # from claude code, codex, gemini, opencode, etc 
Pull from Scott using this planspace and start building: https://app.tryscott.ai/workspace/9579e73f-8292-42ea-8d2f-5d390a8f867e
Use it when a planspace has enough team alignment to guide implementation.

​
What pull includes

The default pull output includes:
  • the current document
  • relevant document versions
  • comments and review context
  • reviewer turns and approval state
  • connected source summaries
  • commits and PR context when available
  • conversation history needed to understand the plan
When you only need the headline document and review state, ask your agent for a summary-only pull: # from claude code, codex, gemini, opencode, etc 
Pull a summary from Scott for this planspace: https://app.tryscott.ai/workspace/...

​
Agent prompt

You can ask your coding agent: # from claude code, codex, gemini, opencode, etc 
Pull the project requirements from this planspace and start building: https://app.tryscott.ai/workspace/...

​
Execution workflow

  1. Confirm the planspace has the right comments and approvals
  2. Pull the planspace into a fresh agent thread
  3. Ask the agent to restate the implementation plan before writing code
  4. Execute against the pulled context
  5. Put the planspace URL in the PR description so the Scott GitHub App can connect code back to design intent

​
Listing recent planspaces

# from claude code, codex, gemini, opencode, etc 
List my recent Scott planspaces so I can choose which one to pull.
Use this when you know the work exists in Scott but do not have the URL handy.