Spec.pm is a tool for writing product requirements. It’s a structured wiki that is specifically designed for product and development teams. It syncs with Pivotal Tracker so you don't have to manually break your spec into tickets.
It's used to communicate a complex feature to a development team. A collection of user stories that make up a complex feature is called an epic. Spec.pm is for writing the user stories that make up an epic. Learn how to write a spec.
A spec is made up of stories
When you add a story, it's pre-populated with three sections. User Story, Logic, and Acceptance Criteria. Learn about these sections.
Spliting a story into frontend and backend is useful when the development team isn't full stack. This is especially true when doing mobile development.
You can drag and drop stories around the page. A spec is like a narrative you are telling the developers. Order your stories in a way that allows them to fully grasp how all the stories work together.
When you sync, all stories are added to a Pivotal Tracker project. Any change to a story in Pivotal Tracker automatically updates the story in Spec.pm, and vice versa. This keeps the spec up-to-date, increasing it's utility as documentation.