feature spec is a new community for product managers to swap best practices for creating technical specs. it's also a place to discover how some of our favorite products and features were conceived.
- new to writing specs? start with our boilerplate.
- need some inspiration? view an example.
- want to show off? submit a pull request.
- fomo, a marketing platform
- makeup looks, a community for makeup tutorials
- upc.co, a search engine for UPC barcodes
stash your images inside images/your-project. categorize your spec by industry or category. a few directories have been pre-populated, free to create more. finally, use snake_case when naming folders and files, please.
feature_spec
│ README.md
│ contributors.md
│
└───ecommerce
│ │ your_spec_here.md
│ │ another_spec.md
│
└───b2b_saas
│ │ yet_another.md
│ │ and_another.md
│
└───enterprise
│ │ cant_wait.md
│ │ to_read_these.md
│
└───another_category
│ who_knows.md
│ its_a_mystery.md
- original feature specs from twitter, facebook, google, etc.
- contributions from celebrity PMs (i don't know any, i'm just a guy who drinks iced coffee)
- honor code, please don't prettify an ugly spec to look more badass.
- specs are more interesting if linked to the finished product/feature/announcement... especially if the final version was different than the plan.
- if you have them, include view-only links to wireframes, early designs, or notes. put us in your shoes!
- omissions for security (or embarassment) reasons are OK, but the more raw, the better.
- the more obscure the feature, the less interesting. ideally, submissions are tangible.
- feel free to include post-mortem notes -- why you made a certain decision choice, what got thrown out, etc.
- self promotion OK, just try not to include more than a couple links.
- fork it
- create your spec branch, which may also include a new folder (
git checkout -b my-product-spec
) - commit your changes (
git commit -am 'new spec - your_spec_name'
) - push to the branch (
git push origin my-product-spec
) - Create a pull request