Bridge Start

Plan and execute the next BRIDGE development slice from requirements.json.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/etapsc/bridge --skill bridge-start
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Bridge Start
Source: https://github.com/etapsc/bridge/tree/main/bridge-codex/.agents/skills/bridge-start
Command: npx skills add https://github.com/etapsc/bridge --skill bridge-start

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the initial phase of the BRIDGE development workflow by planning and executing code slices based on defined requirements.

Core Features & Use Cases

  • Slice Planning: Generates a plan for the next vertical slice of development.
  • Execution: Initiates the implementation of the planned slice.
  • Mode Switching: Adapts the AI's operational mode (architect, code, debug) as needed.
  • Use Case: After defining project requirements, use this Skill to automatically plan and start coding the first feature slice, ensuring adherence to the BRIDGE methodology.

Quick Start

Initiate the BRIDGE implementation process by planning and executing the next development slice.

Frequently Asked Questions about Bridge Start

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan and execute the next code slice in an agile development workflow?

To plan and execute the next code slice, this Skill loads project requirements and context to generate a vertical slice plan and immediately initiates its implementation. It manages transitions between architect, coding, and debugging modes to ensure efficient development execution.

What is the BRIDGE methodology for code planning and slice execution?

The BRIDGE methodology is a development workflow that structures implementation through planned vertical code slices. It adapts the AI's operational mode across architecture, coding, and debugging phases to ensure structured execution based on defined project requirements.

Do I need specific project files to start automated slice planning?

Yes, automated slice planning requires a requirements file at docs/requirements.json and a context file at docs/context.json. The Skill loads these project files to determine the next actionable development slice and generate the implementation plan.

How does the workflow switch between architect, coding, and debugging modes?

The workflow switches between architect, coding, and debugging modes automatically during slice execution. Mode switching adapts the AI's operational behavior to match the current development phase, ensuring efficient implementation transitions throughout the planned vertical slice.

Can I use this to automatically plan the first feature slice after defining requirements?

Yes, you can use this to automatically plan and start coding the first feature slice after defining requirements. It reads your project requirements and context to determine the next actionable slice, then generates the plan and initiates execution.

What are the limitations of using an automated slice execution workflow?

The slice execution workflow depends entirely on the accuracy of your docs/requirements.json and docs/context.json files. Without properly defined project requirements and context, the automated slice planning cannot accurately determine the next actionable development step.