{
  "id": 171712,
  "title": "My Work Week Starts Before I Sit Down: Running Kiro Crew as a Technical Program Manager",
  "url": "https://urgent.news/2026/08/05/my-work-week-starts-before-i-sit-down-running-kiro-crew-as-a",
  "topic": "culture",
  "section": "Culture",
  "published": "2026-08-05T11:17:01.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/ktreharrison/my-work-week-starts-before-i-sit-down-running-kiro-crew-as-a-technical-program-manager-3fgp"
  },
  "original_language": "en",
  "account": "My work week begins before I even sit down at my computer, thanks to Kiro Crew, a persistent agent workspace built on Kiro. I've been using the internal version since April, and it has completely transformed the way I perceive AI in the workplace. Kiro Crew is not just a tool; it's a colleague who's been working diligently all along, waiting for me to arrive.\n\nThe agent workspace runs around a dozen scheduled jobs on my behalf, taking care of tasks such as preparing my morning brief, monitoring releases and metrics, synchronizing task trackers and reviews, and alerting me only when something requires my attention. It maintains months of memory, learning from my projects, writing rules, and decisions, always ready to assist without repeating mistakes.\n\nWhat surprised me most about Kiro Crew is not its speed, but the scope of its capabilities. Initially built as a side project by three engineers, it has now grown to be maintained by a community of more than 39,000 builders, with nearly 500 contributors shipping 597 updates in just six months. I am among those roles, prototyping features, reviewing architecture, and ensuring one change lands everywhere it needs to, from task boards to monthly reviews to launch announcements.\n\nThe key to Kiro Crew's success lies not in the technology itself but in making my own decision-making process explicit enough to delegate. The months I spent teaching the system my rules, what good writing looks like, which data sources to trust, and when to interrupt it were crucial for its performance. For instance, while the agent built an adoption chart for different roles, it initially contained errors due to incorrect data interpretation. The solution was simple - I explicitly defined the rules to avoid such mistakes in the future. Now, the agent spends less time producing analysis and more time ensuring the analysis adheres to the established standards.\n\nKiro Crew's code is now open source, allowing you to encode your judgments into it. Whether you build software every day or have never touched a terminal, Kiro Crew is designed to meet you where you are. Start by teaching it one decision you make every week, and let it take over from there. The journey begins with https://kiro.dev/crew and its source code available at https://github.com/kirodotdev/KiroCrew. You can also join the conversation on Kiro Crew's Twitch channel at https://twitch.tv/kirodotdev.",
  "summary": "The tool I have quietly run my work week on is now open source. Kiro Crew is a persistent agent workspace built on Kiro. I have been on the internal version since April, and it changed how I think about what AI at work actually is. A while back I wrote about terminal productivity as a TPM and how far the command line can take a non-engineer. This is the next chapter: the terminal now runs itself.…",
  "key_points": [
    "Kiro Crew, AI workspace, transforms work week since April",
    "Agent workspace handles 12+ scheduled jobs, maintains memory",
    "Community of 39,000 builders maintains Kiro Crew with 500+ contributors"
  ],
  "editors_take": null,
  "illustration": "https://urgent.news/ill/171712.png",
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}