Greenfield support

[leandrostasi-jt]

The current agents and SDD skills are mostly brownfield. They are good for adding features to an existing repo, but not for turning a pile of .md product/domain notes into a brand-new project.

The current flow is feature-first:

• Agents are planner, implementer, reviewer, antagonist, tdd-guide, tech-lead in README.md:24.
• /sdd-research explicitly inspects an existing repository and records code evidence in rules/sdd/workflow.md:17.
• planner requires spec.md, research.md, and delivery_artifacts/*.md, with research.md as repository evidence in agents/planner.md:35.
• sdd-refine uses a brownfield Change Set: Added / Modified / Removed / Unchanged in skills/sdd-refine/SKILL.md:102.
• There is only a small greenfield hint under “Skeleton Projects” in rules/common/patterns.md:3.

Gap

For greenfield, the missing workflow is:

many .md source docs
-> source inventory
-> project brief
-> resolved requirements
-> architecture decisions
-> scaffold/foundation plan
-> first vertical slice
-> normal SDD execution

The current /sdd-research step is wrong for that because there may be no codebase yet. It should be replaced or complemented by a corpus-research step that reads the .md files and extracts requirements, contradictions,
decisions, and unknowns.

Recommended Addition

Add a separate greenfield workflow, probably under:

rules/greenfield/workflow.md
skills/greenfield-start/SKILL.md
skills/greenfield-research/SKILL.md
skills/greenfield-architecture/SKILL.md
skills/greenfield-delivery-artifacts/SKILL.md
agents/scaffolder.md

Suggested flow:

/greenfield-start
-> source_inventory.md
-> project_brief.md

/greenfield-research
-> requirements.md
-> contradictions.md
-> open_questions.md

/greenfield-architecture
-> architecture.md
-> docs/adr/*.md
-> project command/validation rules

/greenfield-delivery-artifacts
-> delivery_artifacts/*.md

/sdd-facts or /greenfield-facts
-> facts/*.md

planner
-> plan.md + plan/tN.md

/execute-plan
-> scaffold + vertical slices + validation

Important Adjustment

The planner/executor rules need one greenfield exception: task files must distinguish files to create from files expected to already exist. Current SDD drift guard says to stop if a planned file does not exist, which
is correct for brownfield but wrong for scaffold tasks.

So greenfield task files should have explicit sections like:

Files To Create

Files To Modify

Files That Must Already Exist

The existing agents can cover part of it:

• tech-lead: can research and plan, but it is generic and read-only.
• planner: useful after the greenfield artifacts exist.
• implementer: useful once there is an approved plan.
• reviewer / antagonist: still useful after scaffold or first slice exists.

The missing role is a greenfield architect / project bootstrapper.

I would add one new agent:

@greenfield-architect

Its job:

• Read many .md source files.
• Build a source inventory.
• Extract requirements, constraints, contradictions, and open questions.
• Propose the initial product/domain model.
• Recommend architecture, stack, folder structure, and validation commands.
• Identify ADRs that must be recorded.
• Produce a scaffold-ready plan, but not implement code.

May be greenfield is not the best name. new project?