Update spec

[derek-palmer]

Summary by CodeRabbit

• Documentation

  • Standardized specification references across documentation
  • Added comprehensive design documentation for agent skill/plugin packaging and distribution workflows

• Specification Updates

  • Formalized new phase for skill/plugin distribution design
  • Extended specification with constraints for prompt-first documentation workflow
  • Updated phase roadmap with revised task prioritization

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 50f67f77-5813-4df9-afed-af68aac5367a

📥 Commits

Reviewing files that changed from the base of the PR and between eed7566 and 1bbadc7.

📒 Files selected for processing (8)

• AGENTS.md
• README.md
• SPEC.md
• codeforerunner_v2_handoff.md
• docs/agent-distribution-design.md
• docs/editor-agent-setup.md
• docs/getting-started.md
• docs/roadmap.md

---

📝 Walkthrough

Walkthrough

This PR standardizes the project specification file from codeforerunner_spec.md to SPEC.md across all documentation, formalizes the specification with new constraints and invariants for skill/plugin design, introduces a dedicated P4 phase for skill/plugin distribution, defers thin runtime wrappers to P5, marks earlier phases as complete, and documents the comprehensive agent packaging design.

Changes

Spec standardization and phase roadmap

Layer / File(s)	Summary
Spec file standardization across docs AGENTS.md, codeforerunner_v2_handoff.md, docs/editor-agent-setup.md, docs/getting-started.md	All references to codeforerunner_spec.md are updated to SPEC.md as the canonical source of truth for agent guidance, handoff instructions, and phase tracking.
SPEC.md formalization: constraints, invariants, and phase split SPEC.md	Constraint C7 routes skill/plugin packages through prompt pack/current files without claiming runtime support yet; invariant V8 requires design to avoid manual prompt discovery and prevents claiming installed package support prematurely. SPEC.md is established as the canonical I.spec tracker, with I.future-skill-plugin designated as a future surface. The single "thin wrappers" phase is split into P4 (skill/plugin distribution design) and P5 (thin runtime wrappers with deferred CLI/MCP/hooks). The expanded task table moves phase/task tracking into SPEC.md and adds new P4 tasks for canonical skill source creation, Codex/Claude plugin packages, and an idempotent installer.
Project documentation alignment with new phases README.md, docs/roadmap.md	README references are updated to SPEC.md and expanded with a new P4 milestone for skill/plugin distribution. The roadmap marks P0 through P3 as complete with their associated descriptions, establishes P4 and P5 as planned phases with guidance on packaging constraints and surface stability, and confirms SPEC.md as the authoritative phase source.
Agent distribution design documentation docs/agent-distribution-design.md	A new design document specifies the packaging and workflow for making codeforerunner installable as agent skills/plugins. It defines directory layout, installer/uninstaller/doctor behavior, agent instruction contracts (prompt sources, scanning, config naming, reporting, safety), target package conventions for Codex, Claude Code, and generic agents, validation expectations, and open implementation questions.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

• derek-palmer/codeForerunner#8: Directly related as the main specification and phase-plan update that introduces the P4 skill/plugin distribution phase and supporting design constraints.

Poem

🐰 From spec files renamed to phases new,
Distribution dreams now coming through,
P4 packages hop in view,
While P5 wrappers wait their queue—
The roadmap's honest, the path rings true!

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Update spec' is extremely vague and generic. While it technically relates to changes in SPEC.md and spec references throughout the PR, it fails to convey the actual scope and purpose of the changes—which involve standardizing spec file naming (codeforerunner_spec.md → SPEC.md), formalizing a prompt-first workflow with new constraints/invariants, adding a P4 skill/plugin distribution phase, and introducing agent distribution design documentation.	Consider a more descriptive title like 'Standardize spec file naming and add skill/plugin distribution phase' or 'Rename spec file and formalize prompt-first workflow with P4 distribution phase' to better communicate the multi-faceted nature of these changes.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch update-spec

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch update-spec

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

• Generate code and open pull requests
• Plan features and break down work
• Investigate incidents and troubleshoot customer tickets together
• Automate recurring tasks and respond to alerts with triggers
• Summarize progress and report instantly

Built for teams:

• Shared memory across your entire org—no repeating context
• Per-thread sandboxes to safely plan and execute work
• Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}