vqdungwork/pica

From the brief to the shipped product. Analyse the domain and its sector, design in HTML at every viewport you declare, verify by measurement rather than opinion, then estimate, architect, build, test and release. Ten specialists, each pricing its own work, 154 checks that fail closed, four gates enforced by hook.

pica analyst: elicitation, AS-IS and TO-BE, business rules, the domain model, and a PRD a non-technical reader follows. Carries a 28-sector knowledge base: who the stakeholders are, which colours the sector has already spent and why, the design tradition it settled on, and what it treats as a defect regardless of the brief. Fails closed on a sector it does not cover.

pica architect: feasibility before anything is promised, C4 diagrams, architecture decision records, and non-functional requirements stated as numbers.

pica content: the words. Glossary-bound terms, every state written, length-realistic copy, and mock data that is not quietly wrong.

pica core: intake, the contract, the state schema, and every approval gate.

pica design QA: heuristic evaluation fanned out to independent evaluators, cognitive walkthrough, and the build-versus-design comparison nobody owns.

pica developer: build the approved design into working code. The API contract as a seam with its errors, four places state can live, every failure shaped so the copy reaches it, accessibility in code, and a performance budget with the condition it holds under.

pica discover: who uses it and what actually hurts, who can veto it and what they fear, what the field charges, and a market size derived from factors rather than asserted.

pica estimate: three-point effort by role, a work order derived from the deadline, and the effort record that makes the next estimate better than this one.

pica figma: port an approved package or rebuild an existing Figma file, annotate it, and verify it by measurement.

pica html: build each work package at every declared viewport and measure it before approval.

pica implementation: the definition of done for building, reviewing, testing and releasing what was designed. Owns the standard, not the coding agent.

pica model: what it costs to build, what it costs to run for two years, what it plausibly returns, and the price fence that stops every buyer picking the cheapest tier.

pica qa: the shape of the suite and who owns each layer, one end-to-end test per use case, every business rule asserted, a regression test that failed before it passed, and a release gate that reads severity rather than a count.

pica research: audit the named sources and derive tokens with provenance. Measures shipped products across the nine foundations, records typography by role rather than by size, and refuses concept sites as evidence.