development-crew

Shared design principles for all technical agents. Load these when you need cross-cutting design standards without loading a full specialist (Architect, Implementer, or Code Reviewer).

Architecture formalizer. Takes a brainstorm brief and produces a formal architecture specification grounded in the project's tech stack and any available skills. Sits after Rubber Duck and before Implementer in the pipeline.

Code review specialist. Validates implementations against architecture specs, project conventions, and any loaded skills. Read-only, never modifies code. Sits at the end of the pipeline after the Implementer.

Builder. Takes an architecture specification and implements it, writing production code, tests, and configuration matching the project's conventions and any available skills. Sits after Architect and before Code Reviewer in the pipeline.

Brainstorming sparring partner. Helps explore vague ideas, challenge assumptions, and widen the solution space before committing to formal decisions. Sits before the Architect in the pipeline. Invoke when you have a vague idea, want to explore trade-offs, or need to think through a problem before formalizing.

Bootstrap skill that teaches how to use the Development Crew skill pipeline. Explains the four specialist skills, when to invoke each one, and how the pipeline flows from brainstorming to code review.