adapt agile knowledge work

The problem

Standard Agile frameworks designed for software engineering often fail when applied to research, policy, and education. Forcing knowledge work into rigid two-week sprints or software-centric user stories creates "Agile theatre" that ignores intellectual depth and disciplinary quality.

What it does

• Diagnoses existing workflows to identify friction, hidden bottlenecks, and feedback delays.
• Designs custom iterative project methods with flexible cadences suited to research and strategy cycles.
• Builds prioritized work queues focused on learning, evidence, and validated assumptions rather than just task volume.
• Defines completion criteria that respect domain-specific standards like research ethics, pedagogical alignment, and regulatory compliance.
• Facilitates process reflection to adjust methods when uncertainty high or stakeholder access is infrequent.

Why this beats prompting it yourself

General LLMs often default to generic Scrum or Kanban templates that don't translate to non-technical fields. This skill applies a specific "Knowledge Work Cycle" logic that protects intellectual integrity and avoids the overhead of unnecessary daily stand-ups or story points.

Use cases

• Designing a research project workflow that balances deep inquiry with stakeholder feedback milestones.
• Adapting iterative delivery for policy development requiring multi-stage consultation and legal review.
• Structuring a learning design project where increments are validated by learner evidence.
• Coaching a strategy team to manage high-uncertainty work without using software-specific roles.