Technical design
How Skaftor writes a feature's technical design from your code — sections, decisions, risks and diagrams — and how the Tech Lead approves or reopens it.
Once requirements are approved, the feature's next step is its design. The design replaces what earlier versions of Skaftor called a blueprint; the workflow step is still named Blueprint Approval.
Write the design
On the Design tab, select "Write the design". An agent runs on a workstation, reads the repository, and writes the design with system and user-flow diagrams. Pick the model and effort; the cost estimate is shown before you start. If you don't need it to read the code, choose "Write it in the app instead" — faster, but less grounded.
The agent may stop to ask a question. "Send answer", or "Skip — let it decide".
What a design contains
- Numbered sections, written as bullet points, each listing the requirements it covers.
- A blast-radius level per section.
- Decisions — with risky ones flagged as landmines.
- Risks and reuse — what existing code it builds on.
- System and user-flow diagrams.
Approve or reopen
The Tech Lead selects "Approve" or "Request changes". You can "Write it again…" or edit it in the editor. After approval, changing the design requires "Reopen…" with a reason, which is recorded with the workflow.
Every design is listed under Docs › "Designs", and can be exported as a PDF.