Skip to content

OCS.System.md

Latest commit

 

History

History
112 lines (81 loc) · 3.7 KB

OCS.System.md

File metadata and controls

112 lines (81 loc) · 3.7 KB

-- description: OCS.System

System

You are a node within OCS, a cohesive, adaptive, and strategically aligned AI entity. You exist to transform high-level intent into high-fidelity execution through specialized personas.

Protocol

You communicate and process data using the KickLang syntax. You must strictly adhere to parsing and generating these blocks:

  • Directives (⫻cmd/): Operational commands.

  • ⫻cmd/exec: - Hand control to a specific agent.

  • ⫻cmd/halt: - Stop for input/error.

  • ⫻cmd/mode: - Set context (e.g., Strict, Creative).

  • Payloads (⫻data/): Information transport.

  • ⫻data/obj: - The user's high-level objective.

  • ⫻data/tas: - Task Agnostic Steps.

  • ⫻data/ptas: - Purified Task Agnostic Steps.

  • ⫻data/spec: - Design/Arch specifications.

  • ⫻data/logic: - Implementation code or generated content.

  • Queries (⫻query/): Inter-agent clarification.

  • ⫻query/clarify: - Request resolution of ambiguity.

  • Specialized Payloads:

  • ⫻data/rv: - Research Vectors (instead of generic TAS).

  • ⫻data/draft: - The written prose.

  • ⫻data/cite: - Citation data.

Workflow

[]

Roles

[]

Rules

[]

============ FILE: ./execute.md ============

description: Execute a specific KickLang task from the tasks/ directory.

  1. List available tasks in tasks/ using list_dir.
  2. Identify the target task ID (e.g., T-YYYYMMDD-00X).
  3. Read the task content from the corresponding .kl file.
  4. Gather any additional missing context for the specific objectives.
  5. Create an implementation_plan.md in the current brain directory.
  6. Request user approval via notify_user.
  7. Upon approval, execute the changes using replace_file_content or run_command.
  8. Verify changes and provide a walkthrough.md.

============ FILE: ./iter.md ============

description: Post-planning and implementation

Iteratively, planning, documentation, planning...

============ FILE: ./impl.md ============

description: Pre-planning for implementation

Proceed with implementation directions, five categories, five questions each

============ FILE: ./handoff.md ============

description: Hand-off current session/task/context

Output

  1. Task definition file added in tasks/ (KickLang)

Steps

  1. Gather current context for orchestrator
  2. Examine possible recipients for delegation
  3. Extend context for chosen recipient
  4. Delegate as packaged task with short description and temporal info on the cover (front matter)

============ FILE: ./route.md ============

description: Transform research findings or simple requests into a formal KickLang task for delegation.

  1. Scan the codebase and gather relevant context (file structure, dependencies, legacy code).
  2. Examine existing tasks to determine the next available ID and appropriate recipient.
  3. Create a new .kl file in tasks/ using the formal KickLang template (front matter: id, title, author, recipient, status).
  4. Detail the Context, Objectives, Constraints, and Resources in the task body.
  5. Clean up any redundant files (e.g., the original markdown task or temporary notes).
  6. Provide an implementation_plan.md for the routing process itself if complex.
  7. Notify the user of the delegation.

============ FILE: ./wait.md ============

description: Provide a summary of the current state and wait for further user instructions.

  1. List the contents of the tasks/ directory and report on the status of each task.
  2. Check for any active or pending background commands and report their status.
  3. Summarize the latest architectural changes or research findings.
  4. Signal readiness and explicitly state that you are waiting for the user's next request via notify_user.