Spec-Driven iOS Development

Vectorby Mobiman

A meta-prompting and context engineering development system for iOS.

$npx @mobiman/vector
$claude --dangerously-skip-permissions
💡

Already have a codebase? Run /vector:map-codebase first. It spawns parallel agents to analyze your stack, architecture, conventions, and concerns. Then /vector:new-project knows your codebase — questions focus on what you're adding, and planning automatically loads your patterns.

Orchestration

Every stage uses the same pattern: a thin orchestrator spawns specialized agents, collects results, and routes to the next step.

Research
Orchestrator

Coordinates, presents findings

Agents

4 parallel researchers investigate stack, features, architecture, pitfalls

Planning
Orchestrator

Validates, manages iteration

Agents

Planner creates plans, checker verifies, loop until pass

Execution
Orchestrator

Groups into waves, tracks progress

Agents

Executors implement in parallel, each with fresh 200k context

Verification
Orchestrator

Presents results, routes next

Agents

Verifier checks codebase against goals, debuggers diagnose failures

The result: You can run an entire phase — deep research, multiple plans created and verified, thousands of lines of code written across parallel executors, automated verification against goals — and your main context window stays at 30–40%. The work happens in fresh subagent contexts. Your session stays fast and responsive.

Commands

Core Workflow

/vector:new-project [--auto]Full initialization: questions → research → requirements → roadmap
/vector:discuss-phase [N] [--auto]Capture implementation decisions before planning
/vector:plan-phase [N] [--auto]Research + plan + verify for a phase
/vector:execute-phase <N>Execute all plans in parallel waves, verify when complete
/vector:verify-work [N]Manual user acceptance testing
/vector:audit-milestoneVerify milestone achieved its definition of done
/vector:complete-milestoneArchive milestone, tag release
/vector:new-milestone [name]Start next version: questions → research → requirements → roadmap

UI Design

/vector:ui-phase [N]Generate UI design contract (UI-SPEC.md) for frontend phases
/vector:ui-review [N]Retroactive 6-pillar visual audit of implemented frontend code

Navigation

/vector:progressWhere am I? What's next?
/vector:helpShow all commands and usage guide
/vector:updateUpdate Vector with changelog preview
/vector:join-discordJoin the Vector Discord community

Brownfield

/vector:map-codebase [area]Analyze existing codebase before new-project

Phase Management

/vector:add-phaseAppend phase to roadmap
/vector:insert-phase [N]Insert urgent work between phases
/vector:remove-phase [N]Remove future phase, renumber
/vector:list-phase-assumptions [N]See Claude's intended approach before planning
/vector:plan-milestone-gapsCreate phases to close gaps from audit

Session

/vector:pause-workCreate handoff when stopping mid-phase
/vector:resume-workRestore from last session

Utilities

/vector:settingsConfigure model profile and workflow agents
/vector:set-profile <profile>Switch model profile (quality/balanced/budget/inherit)
/vector:add-todo [desc]Capture idea for later
/vector:check-todosList pending todos
/vector:debug [desc]Systematic debugging with persistent state
/vector:quick [--full] [--discuss] [--research]Execute ad-hoc task with Vector guarantees
/vector:health [--repair]Validate .planning/ directory integrity
/vector:statsDisplay project statistics — phases, plans, requirements, git metrics