Draft Retrospective Action Items
Have finished a sprint retrospective and need to turn the team's observations into specific, ownable action items.
Prompts for your job
Have finished a sprint retrospective and need to turn the team's observations into specific, ownable action items.
Need to create structured requests for proposals or quotes to solicit detailed vendor responses.
Use this when you're answering a formal RFP and need well-structured first drafts you can edit.
Need a spec document covering requirements, interfaces, and tolerances.
Need to define the signals and sequence between a robot and a PLC.
Are structuring robot behavior modes and want clean transition logic.
Need a first draft of authorized testing boundaries, contacts, and legal constraints for a client.
Need to capture design intent, connections and assumptions before drawing a schematic.
Need team instructions for storing and rotating credentials.
Use this when a new campaign targets your industry and you want to warn staff and partners quickly.
Are preparing a design review or gate check for a new service or integration and need a structured security and compliance checklist.
Are combining IMU, encoder, and vision data and need a defensible fusion approach before you commit to code.
Are adding a new sensor to an embedded design and need a step-by-step plan covering bus setup, timing, calibration and error handling.
Need a starting point for a standard token, NFT, or vault contract and want the imports, state, and function stubs drafted quickly.
Need a concise sprint goal that connects selected backlog items to a business outcome.
Are preparing a structured planning session for the team.
Need a regular update on progress and risks for a sprint.
Need a clear narrative for the demo and review discussion.
Need to explain a model's behaviour, performance and risks to non-technical partners in plain English.
Need to describe how controllers, sensors, and networks connect.
Use this when your team needs shared rules for writing and reviewing prompts.
Know the control area and need concrete procedures to test it.
Have a user story that needs clear, testable conditions before the team refines it.
Have a feature idea and need user stories in the standard role-goal-benefit format.