Rebuild markdown after recent skill definition changes

pivotal-cf · May 23, 2019 · d3f963d · d3f963d
1 parent 94b11ac
commit d3f963d
Show file tree

Hide file tree

Showing 4 changed files with 4 additions and 6 deletions.
diff --git a/domain-expertise.md b/domain-expertise.md
@@ -29,7 +29,7 @@ One example of success in this area: You are trying to decide how to implement a
 <td valign="top"><ul>
   <li>Has working knowledge about the product their team is building.</li>
 
-  <li>Is learning about how other teams/downstream consumers/customers use their product</li>
+  <li>Has working knowledge about how other teams/downstream consumers/customers use their product</li>
 
   <li>Relates stories in the backlog to downstream consumers it would affect</li>
 

diff --git a/project-leadership.md b/project-leadership.md
@@ -23,8 +23,6 @@ One example of success in this area: You are anchoring your team. You’ve been
   <li>Volunteers for facilitating team meetings</li>
 
   <li>Discusses team “things” with their anchor (eg: team process, team health/morale, product, architecture)</li>
-
-  <li>Is comfortable letting go of a priority that they have worked on</li>
 </ul></td>
 </tr>
 
@@ -45,7 +43,7 @@ One example of success in this area: You are anchoring your team. You’ve been
 
   <li>Able to anchor small/medium-sized teams with well-defined product priorities and technical direction</li>
 
-  <li>Recognizes when their pair or team would benefit from cutting scope, and builds consensus for it</li>
+  <li>Recognizes when the team would benefit from cutting scope, and helps them get comfortable with it</li>
 </ul></td>
 </tr>
 

diff --git a/technical-decision-making.md b/technical-decision-making.md
@@ -28,7 +28,7 @@ One example of success in this area: You have been noticing a lot of bugs arisin
 <tr>
 <td><strong>P2</strong></td>
 <td valign="top"><ul>
-  <li>Surfaces and discusses various factors (outlined on next page) when approaching a technical decision, with support from other pivots to make the final decision.</li>
+  <li>Surfaces and discusses various factors (e.g. maintainability, extensibility, security) when approaching a technical decision, with support from other pivots to make the final decision.</li>
 
   <li>Makes sound technical decisions that conform to the team's existing architecture or vision.</li>
 </ul></td>

diff --git a/technical-execution.md b/technical-execution.md
@@ -50,7 +50,7 @@ Another example of success in this area: You join a team whose main responsibili
 
   <li>Recognizes and discusses potential anti-patterns</li>
 
-  <li>Can onboard pairs into well-defined stories</li>
+  <li>Clearly and kindly shares context on in-flight work to onboard their pair</li>
 </ul></td>
 </tr>