TASK WEAVE GUIDES
Connect requirements management to tasks and verification
When specifications and task lists live separately, a change makes it harder to identify which work and tests need review. Task Weave helps teams organize the relationships between requirements, specifications, development and verification.
Keep the requirement, its reasoning and its connections
A requirement describes what you want to achieve. A specification defines concrete conditions for achieving it. Development tasks turn the plan into work, while verification checks whether the conditions were met. Being able to follow those relationships is traceability.
The aim is not simply to write more documentation. It is to show which requirement supports a specification and how that specification connects to implementation and testing. Task Weave brings those relationships into the same overall view as everyday work.
A robotics example
- Goal: Prune roadside trees safely.
- Requirement: Protect pedestrians.
- Specification: Stop pruning when a person is detected.
- Development: Implement person detection and stopping.
- Verification: Test stopping on a simulated sidewalk and record the result.
This is a fictional illustration. Your team must define safety requirements and acceptance criteria for its product and environment. Using a management tool alone does not guarantee safety or compliance.
Separate finished work from satisfied requirements
Completing an implementation does not itself prove that a requirement has been met. Task Weave treats development and verification separately, alongside schedules and dependencies. Outstanding test questions should remain visible even when implementation progress is complete.
Record alternatives and reasons for change
Research and prototyping often involve comparing several approaches before making a conditional choice. Keep notes, reference URLs and selection reasons, and distinguish completed research from a finished product. When something changes, follow the related requirements, specifications, work and verification with your team. Task Weave does not automatically determine every impact.
Explore the sample
The interactive browser demo includes fictional robotics and approach-comparison examples. Switch between requirements, specifications, the structure map and timeline to explore how they connect. Demo edits are not saved.