BuildSolid

buildsolid-orchestrator helps when entry is ambiguous or work needs coordination. Read current accepted artifacts before choosing the earliest applicable stage. A clear, focused request can enter its matching skill directly.

Stated intent, profile, mode, and applicable entry point.

founder-discovery pressure-tests the idea and differentiation, separating evidence from assumptions. Existing projects return to full discovery only when intent, audience, or product direction changes.

founder-intent.md and discovery.md at the depth the work needs.

idea-compressor makes the audience, wedge, problem severity, and current alternatives clear enough for later scope and acceptance decisions. Unproven claims stay visible as assumptions.

product-thesis.md and problem-statement.md.

mvp-scope turns the thesis into must-haves, non-goals, and a proportionate time or effort budget. Small changes can carry the same information in an adequate compact contract.

mvp-scope.md and non-goals.md, or adequate compact sections.

ux-minimalist looks for fewer screens and clearer flows, including success, failure, and edge cases. UX depth follows the affected surface; an internal utility does not need invented screens.

user-journeys.md and design.md when applicable.

intelligence-layer-architect defines capabilities, prompts, models, and data flow as a system layer. This stage is required whenever AI is load-bearing, in any profile. No artifact is needed solely to say that AI is inapplicable.

intelligence-layer.md when AI is load-bearing.

technical-planner records the architecture and its constraints. starter-stack-advisor is an optional helper when the builder wants an opinionated minimal default. Architecture depth follows the actual change.

architecture.md or adequate compact architecture sections.

spec-planner produces or maintains spec.md and plan.md. Bounded work can use one accepted Markdown contract with intent, scope, approach, tasks, acceptance, and allowed effects. Missing material content still blocks implementation.

Accepted spec.md and plan.md, or adequate compact sections.

task-breakdown gives each task actionable scope, files, inputs, acceptance, status, and dependencies at the selected profile's depth. Existing Project Change needs a clear impact analysis before tasks are drafted or updated.

tasks.md or the compact contract's task section.

implementation-executor handles scoped features, bugs, refactors, and bounded experiments. project-investigator supports read-only questions; project-verifier establishes observable behavior and coverage. Record the actual revision or dirty state, results, and limits. Material contract drift returns to its owner before execution continues.

Changed software, honest task status, and revision-bound verification evidence.

qa-reviewer runs before security-reviewer; project-verifier can support criterion-linked evidence. Separate passed, failed, unverified, and inconclusive results. Same-scope defects return to implementation and affected checks are repeated after repair. Review can inspect incomplete work without accepting it as complete.

Criterion-linked findings, coverage limits, and applicable acceptance or remediation.

deployment-manager produces planning artifacts only and stops at deployment.md. It records how the project should ship and recover; the project's own authorized work performs any actual deployment or infrastructure changes. Secret values stay out of the repository.

deployment.md covering applicable rollout and operational commitments.

launch-prep records applicable readiness conditions in launch-checklist.md. Positioning, first-user planning, and metrics appear when the event needs them. The skill prepares guidance and checks; project work carries out the page, outreach, or deployment under its own authority.

launch-checklist.md with concrete applicable readiness conditions.

Observe and record evidence, diagnose, propose and test, then seek human review. Accept or reject the proposal; accepted changes update artifacts in place and return to the earliest affected stage through Existing Project Change impact analysis. Validate proportionately. workflow-improver supports evidenced workflow learning. Ordinary bugs, review fixes, maintenance, and retries remain same-scope change work.

Evidence, a human decision, an accepted re-entry path where applicable, and validation.