Hi,
It starts with specifications, requirements, feature list...
Then you need some basic knowledge about hardware and HDL to be able to divide the "big task" into a couple of smaller tasks
Then take one (by one) of the smaller tasks and divide them into even smaller tasks.
Do this until you come to a point where every task is so small that it easily can be coded.
At this point you need some deeper knowledge about how to write verilog code.
Often forgotten:
Write the tiny snippets of code
* then test them
* and correct them if necessary
* write documentation
Combine some snippets .. then again test them ... do this until the whole code is finished.
We often see code, schematics, software... written all at once, but they don't work. And the member has no idea what's wrong, can't give no useful error description.
Mind:
* you do the job, you do the sketches, write code
* we help to rectify mistakes, and how to improve it.
Generally: Don't expect that members spend more time for the reply than you show. When you write a single line without details, you have to expect that the replies are also one line without details.
Show your effort, show what you have done, show your ideas, give links to documents..
Klaus