Teacher Wu Yun’s introduction to codex goal is very detailed. I recommend everyone to r...

Teacher Wu Yun’s introduction to codex goal is very detailed.

I recommend everyone to read it.

At the same time, I will share a sample goal command that I verified and sent a few days ago.

You can use it when vibe coding and experience the fun of long tasks.

The goal command /goal suitable for vibe coding advances the current code project to a deliverable and verifiable state.

Prioritize opening up the core functional links, and then handle the necessary experience, testing and document finishing.

Context: This is a code project in continuous iteration.

Please understand the current code structure, existing implementation, testing methods and local change status before deciding on the advancement sequence.

Constraints: - Do not overwrite, roll back or delete my existing local changes unless I explicitly ask - Do not destroy the existing visual style, directory structure and technology selection - Do not introduce unnecessary new dependencies - Do not do large-scale refactoring that is not related to the current goal - Prioritize the existing patterns, components, tools and naming styles of the project Acceptance criteria: - Core functional links can run and be verified - Relevant tests, lint, typecheck or build commands have been run as much as possible - If verification commands cannot be run, an explanation is required Reasons - Necessary documents, comments or configurations have been updated - Final description of completed content, verification results, remaining risks and recommended follow-up matters.

How to advance: - Record the progress of this goal locally to avoid missing important information, and show me the content after completion - Check the current status of the project and the status of the git workspace first - Disassemble the tasks yourself and advance according to priority - Prioritize solving problems that block the core link - Make your own judgment on general implementation details, do not ask me frequently - Synchronize the current status after completing a key stage - Try to do repeatable verification after every important change.

You must pause to ask about my situation: - The core architecture needs to be reconstructed - A large amount of old logic needs to be deleted or the directory structure needs to be migrated - A new database, external service, payment capability or heavy dependency needs to be added - There are multiple reasonable solutions with obviously different consequences - The goal is unclear, and continuing to advance may cause rework

Visual summary

Article argument map

Generated from the post's content graph

Mermaid outline

flowchart LR
  format-long_post["longform note"]
  topic-harness-engineering["harness engineering"]
  topic-memory["memory"]
  topic-tooling["tooling"]
  capability-harness-engineering["harness engineering"]
  market-open-source-builders["open-source builders"]
  format-long_post -->|covers| topic-harness-engineering
  format-long_post -->|covers| topic-memory
  format-long_post -->|covers| topic-tooling
  format-long_post -->|signals| capability-harness-engineering
  format-long_post -->|signals| market-open-source-builders

Visual structure

Essay structure map

Built from summary and key paragraph positions

Mermaid outline

flowchart LR
  thesis["Teacher Wu Yun’s introduction to codex goal is very detailed. I recommend everyone to read it. At the same..."]
  signal["Teacher Wu Yun’s introduction to codex goal is very detailed."]
  operator["Prioritize opening up the core functional links, and then handle the necessary experience, testing and docu..."]
  implication["You must pause to ask about my situation: - The core architecture needs to be reconstructed - A large amoun..."]
  thesis -->|frames| signal
  signal -->|develops| operator
  operator -->|lands in| implication

Source: View the original post