GL

To generate validated project specifications, you run an adaptive pipeline that surveys existing codebases, interviews stakeholders, drafts documents, and reconciles them for consistency. This produces a coherent suite of testable specs aligned with your architectural decisions.

Capturing architectural rationales involves creating per-topic DECISIONS files that explicitly record choices, dependencies, and justifications. This standardizes project decisions into an auditable, repeatable documentation workflow.

Yes, template-driven documentation applies to both greenfield projects and existing codebases. It guides discovery and decision capture through domain packs, ensuring choices are aligned across the documentation suite.

To check for contradictions across a documentation suite, you perform reconciliation passes against the DOC_MANIFEST and DECISIONS files. This process identifies gaps, contradictions, and verifications to ensure consistency.

Yes, YAML frontmatter in SKILL.md is required to start the project scoping workflow. It supports the orchestration of interview, drafting, and reconciliation agents needed to produce consistent documentation.