Abstract: Embodiments enable the selection and application of project plans to user data stores. A project plan having one or more project content items is created according to a pre-defined schema. The project plan is analyzed to identify the project content items that correspond to user data stores available on a computing device. The user data stores include, for example, calendar appointments, tasks, and shopping lists. The project content items are integrated with the user data stores, such as by creating calendar entries, adding tasks, and adding items to the shopping lists. A manifest is defined to describe and record the integrated project content items and the corresponding user data stores. The manifest may also be used to remove or suspend the project plan.

Abstract: Embodiments modify project plans to create customized project plans for a user. A project plan having one or more project content items is created according to a pre-defined schema. The user customizes the project plan by adding, removing, and/or substituting project content items or properties (e.g., adjust the timing for accomplishing tasks). The customized project plan is analyzed to identify the project content items that correspond to user data stores available on a computing device. The user data stores include, for example, calendar appointments, tasks, and shopping lists. The project content items are integrated with the user data stores, such as by creating calendar entries, adding tasks, and adding items to the shopping lists. A manifest is defined to describe and record the integrated project content items and the corresponding user data stores.

Abstract: Embodiments enable the monitoring of project plans and the selection and application of rewards to motivate users. Project plans having one or more project content items are created according to a pre-defined schema. The project plans are integrated with user data stores, such as calendar appointments, tasks, and shopping lists. Progress indicators reflecting a completion status of the project plans are calculated for the project plans. Rewards are selected based on the progress indicators and on user preferences (e.g., collected user activity data). The rewards correspond to milestones associated with the project plans, and are integrated into the user data stores when the user reaches the corresponding milestones.