Public documentation v0.1.0
Progressive-disclosure task specs
How Software Factory writes compact, evidence-backed PM and Kanban task specs.
What changed
Software Factory role profiles now route task-writing doctrine through linked references instead of expanding root instructions into manuals. Root SOUL and profile instructions stay concise: they name the trigger, preserve role boundaries, and point maintainers to detailed references or focused skills.
Why it changed
Progressive disclosure keeps startup context small while preserving the details needed by task authors, reviewers, publishers, installers, and docs maintainers. Workers can scan the goal and mandatory context first, then expand only the referenced detail that applies to the current task.
Task-spec pattern
Task specs should include a title, goal, context index, scope, acceptance criteria, and evidence expectations. The context index separates always-required material from conditional When X, read Y triggers for release packets, source maps, references, or role-specific guidance.
Acceptance criteria quality bar
Acceptance criteria should be clear and concise, testable or objectively verifiable, outcome-focused, measurable where possible, independent enough to validate separately, stakeholder-readable, and linked to evidence. Every non-trivial criterion should state expected proof with an Evidence clause or equivalent wording.
Evidence examples
Useful evidence includes public source paths, quoted snippets, diff summaries, validation command summaries, deployed documentation URLs, and non-secret readback status. Evidence should prove the outcome without requiring private logs, raw board databases, local profile state, credentials, sessions, memories, private notes, private sprite URLs, or checkpoint internals.
Rollout status
The progressive-disclosure task-spec guidance was reviewed, published to the public role profile repositories, reflected by the public Software Factory monorepo profile pointers, and installed into production and meta profile sets with non-secret readback verification.
Public/private boundary
This page describes the public task-writing pattern and summarized rollout outcome only. It omits raw task records, local workspace paths, private profile contents, sessions, memories, credentials, task identifiers, private sprite URLs, and private operational metadata.