Milestone map
Milestone map
3 milestones
Ship a CLI that solves one real problem
2–3 weeks
Build a command-line tool that solves a problem you actually have. Give it clear help text, sensible errors and one install command. Publish it with a licence and a README so a stranger can try it.
Proof required
Link the public repository with a README, licence, install instructions, and a short demo (GIF or recording) of the tool solving the problem.
What gets checked
- Solves a specific problem stated in one line
- --help and error messages are clear
- Installs with one command on a clean machine
Common mistakes
- A tool with no clear problem
- Install steps that only work on your machine
- No licence, so nobody can use it
Powstik Guide
A public CLI tool anyone can install.
Steps
- Write the problem it solves in one sentence.
- Build the smallest version that solves it.
- Add --help, a --version flag and clear errors.
- Publish to a package registry or releases page.
- Add a README with a demo and a licence.
Template
README outline # tool-name — one-line problem it solves ## Install (one command) ## Usage (3 examples) ## Options ## Licence
What gets sent back
- No stated problem.
- Install steps that fail on a clean machine.
- No licence.
Resources
Foundationstart here
Depthgo deeper
What a verifier looks for
- Install it on a clean machine
- Run --help and a bad input
- Check the licence file
You'll sign in first, then come straight back here.
Put it in front of real users
2–4 weeks
Tell the people who have this problem where to find your tool. Answer every issue, and ship at least two releases based on feedback. Stars come from people who find it useful, not from asking friends.
Proof required
Link at least two tagged releases, list where you shared the tool, and link at least three issues or discussions from people you don't know.
What gets checked
- Shared in places the target users actually are
- Two releases with changelogs driven by feedback
- Three or more issues or comments from strangers
Common mistakes
- Asking friends to star it
- Ignoring issues
- No releases after launch
Powstik Guide
Two feedback-driven releases and real user issues.
Steps
- List three places your target users talk.
- Post a short, honest description with a demo.
- Reply to every issue within a few days.
- Group fixes into a versioned release with notes.
- Repeat for a second release.
Template
| Where shared | Date | Link | Response | |--------------|------|------|----------| Release notes ## vX.Y.Z - Fixed: (#issue) - Added: (#issue)
What gets sent back
- Stars from people you asked.
- Unanswered issues.
- Fewer than two releases.
Resources
Foundationstart here
Depthgo deeper
What a verifier looks for
- Check release notes link to issues
- Check issue authors aren't the owner's friends
- Look at where it was shared
You'll sign in first, then come straight back here.
Reach 50 stars and write the story
4–8 weeks
Keep improving until the repository passes 50 stars from real users. Then write up what made people use it. The write-up is the evidence that you understand why it worked.
Proof required
Link the repository showing 50+ stars and a write-up (300+ words) on who uses it, what drove adoption, and what you'd change.
What gets checked
- 50+ stars, not from a star-swap group
- Write-up names the channel that drove most stars
- Honest note on what didn't work
Common mistakes
- Buying or trading stars
- A write-up with no data
- Stopping maintenance after hitting 50
Powstik Guide
A tool with 50 real stars and an adoption write-up.
Steps
- Track stars by week against where you posted.
- Double down on the channel that worked.
- Keep releasing fixes users ask for.
- Write up who uses it and why.
Template
Adoption write-up Who uses it: Channel that drove most stars (with dates): What users asked for most: What didn't work: What I'd change:
What gets sent back
- Stars from swap groups or bots.
- No channel data.
- No maintenance after launch.
Resources
Foundationstart here
Depthgo deeper
What a verifier looks for
- Scan stargazers for obvious fake accounts
- Check the write-up cites real channels
- Check recent commits
You'll sign in first, then come straight back here.