Add spike protocol for technical feasibility exploration

[waleedkadous]

Feature Request

Add a spike protocol for time-boxed technical feasibility exploration. Lighter than experiment (no formal hypothesis), heavier than ad-hoc (structured output).

Purpose

Determine whether an approach is technically feasible before committing to a full SPIR project. Answer questions like "can we do X?" and "what would it take?"

Phases

1. Research — Explore the problem space, read docs, examine existing code, identify constraints
2. Iterate — Build a minimal proof-of-concept, try approaches, hit walls, pivot
3. Findings — Document what was learned: feasibility verdict, recommended approach, risks, estimated effort for full implementation

Protocol Properties

• No spec/plan required (input.required: false)
• No consultation by default (speed over rigor)
• No gates — runs autonomously to completion
• Time-boxed — builder prompt should emphasize staying focused and stopping when the question is answered
• Output: A findings document in codev/reviews/ (or a new codev/spikes/ directory?)
• Soft mode only — no porch orchestration needed

New Label

Added spike label for GitHub issues that use this protocol.

Files to Create

• codev-skeleton/protocols/spike/protocol.json
• codev-skeleton/protocols/spike/protocol.md
• codev-skeleton/protocols/spike/builder-prompt.md
• codev-skeleton/protocols/spike/templates/ (findings template)

[waleedkadous]

Spec feedback: The 3 phases (research, iterate, findings) should be guidance in the builder prompt only — not formal porch phases in protocol.json. This is soft mode only, no porch orchestration. Keep protocol.json minimal (no phases, no gates). The builder prompt describes the workflow.