Discuss a concrete project
Start with the smallest useful workflow
Use this guided entry point when you have a repeated task, a creative pipeline or a review bottleneck that should become a bounded tool.
- 01 Name the repeated workflow and what a good result would change.
- 02 List the tools, files, APIs or approval roles involved.
- 03 Identify the point where errors, delays or uncertainty repeat.
- 04 Mark what must remain private, local, manual or human-approved.
A first message is enough for scoping. Do not send credentials, private repositories, confidential datasets or production secrets.
Discuss a concrete project
A safe first-message brief
Use this shape when you write. It gives enough context to scope the work without sharing secrets, credentials or private repositories.
- Workflow The repeated task is...
- Inputs The files, tools or APIs involved are...
- Failure point The place it usually breaks is...
- Human decision A person must still approve...
- Private boundary Do not access or store...
Discuss a concrete project
What happens after you write
The first reply should clarify scope, risk and the smallest useful artifact. It is not a request for credentials, private repositories or production access.
- Triage Confirm the workflow, owner, inputs and repeated failure point.
- Boundary check Separate public context from private material and name anything that must stay local.
- Prototype shape Suggest the smallest audit, connector, validator, dashboard or assistant that can prove value.
- Next decision Decide whether to stop, refine the brief or move into a bounded prototype.