34 posts tagged with "productivity"

If your AI workflow still makes you repeat the same instructions in every single chat, that's a tax you don't need to pay. I built Ink and Agency to fix that friction point. It’s a practical skills pack designed to integrate right into Claude—and can be adapted for other agents, giving reusable prompts for writing, planning, triage, architecture design, and just general day-to-day work.

I wanted better outputs with less effort and more consistency across tasks. So I turned repeatable playbooks into discrete skills, each with clear boundaries and predictable behavior.

Why I Built It​

Most agent failures don't happen because the model is bad. They happen because the prompt quality falls apart.

You ask for something broad, get a broad response. Then you spend time correcting it—steering it back on track. That’s fine if you do it once in a while. But when that becomes your daily job, it grinds you down.

Ink and Agency packages task-specific behavior into reusable units. Now, you can route work by intent instead of rewriting the entire process every time.

What's In The Pack​

The repository is structured like a catalog: one folder per skill with a SKILL.md entry point. It gives you practical coverage across areas that teams actually deal with:

• Writing: Drafting, shaping, humanizing, and structuring long-form content.
• Analysis: Codebase explanation, issue triage, and message breakdown.
• Planning: Sprint planning, review reporting, standup prep, and daily briefings.
• Collaboration: Structured critique modes or multi-persona consultation (a "council").
• Workspace: Operations for Obsidian notes, markdown files, canvases, and general vault work.

Quick Start for Claude Users:

git clone git@github.com:risadams/skills.git "$HOME/.claude/skills"

After that, the skills are ready—no extra launcher needed.

The Real Value in Day-to-Day Work​

A good skills pack isn't just a bag of clever prompts. It’s a reliability layer. Here is what changes after you start using one:

• Better handoffs: Tasks are framed consistently, so the output quality doesn't feel random.
• Less context thrash: You stop re-explaining your process in every single chat thread.
• Faster execution: Known task types map directly to known skill patterns.
• Easier team adoption: Every skill has a stable surface area and clear purpose—it’s predictable.

If you work in DevOps, delivery, or product engineering, this pattern hits home quickly. You're already used to turning repeated work into scripts, templates, and automation. Skills are just that move for prompt-driven work.

A Few Quick Examples of Use​

You don't have to write long instructions; you can just ask for the outcome:

• Use break-it-down on this email to explain what it is really saying.
• Run codebase-explain for this module.
• Triage PROJ-1234.
• Run a clarity-council on this design tradeoff.

That's the whole point. You ask for outcomes, not rituals.

The most productive three hours of my week look suspicious from the outside. No meetings, no Slack, headphones in, do not disturb. From the inside, it's the only time I'm actually working.

I don't mean "actually working" as a knock on everything else. I mean it's the only time my brain is in the state where hard problems get solved, where the architecture makes sense, where I stop fighting friction and start making progress. Getting there, for an ADHD brain, is not as simple as closing your email client.

Your team's velocity is stuck. The backlog keeps growing. Everyone's saying you need more developers, but here's the thing — throwing people at the problem often makes it worse. The real leverage comes from identifying and eliminating the constraints that are silently strangling your team's throughput.

You're knee-deep in a feature branch when urgent production fire hits. Instead of stashing, switching, and losing your mental context, what if you could just... open another folder and work on the hotfix immediately? Git worktrees make this possible, and once you experience the workflow, you'll wonder how you ever lived without them.

Unless you've won the lottery or have a trust fund that pays out in premium coffee beans, you probably have a job. Most days, you're likely fine with that arrangement—solving problems, sending emails, and optimizing workflows. But let's be real: even the best jobs come with moments that make you want to delete your professional identity and start fresh.

Your git commit history could be telling an epic tale of how your codebase evolved, or it could be a cryptic collection of "fixed stuff" and "updated things." The difference isn't just aesthetic—it's the line between a repository that teaches and one that confuses. Well-crafted commits don't just track changes; they document your code's journey in a way that helps your team and future you.

Have you ever stared at a Git diff that looks like it was generated by a cat walking across your keyboard? You're not alone. While Git's default diff algorithm works well enough most days, there are times when it produces cryptic, unusable output that leaves you scratching your head.

I stumbled across Git Notes during a late-night debugging session last week, and honestly, I'm slightly annoyed that I hadn't been using this feature for years. If you've ever wanted to attach persistent metadata to commits without changing commit hashes (and who hasn't?), this hidden gem deserves your attention. And while we're exploring Git's underappreciated features, let's also look at Git trailers - another powerful tool for managing metadata in your repositories.

As a Scrum Master with years of experience facilitating retrospectives for development teams, I've discovered that the success of a retro hinges on thoughtful preparation. The right format, the right questions, and the right energy can transform a session from a routine meeting into a powerful tool for team growth and improvement.

In this post, I'll share the key questions I ask myself when planning a sprint retrospective that delivers real value and fosters meaningful change.

Joining an existing team as a new Scrum Master is like being dropped into the middle of a complex ecosystem with its own established patterns and invisible rules. You might be tempted to immediately start "fixing" things based on textbook Scrum implementations or previous experiences. Don't. Instead, invest time understanding the current landscape before making any changes. These teams have history, context, and reasons (good or otherwise) for how they operate. Your first job isn't to change—it's to comprehend.

As a Scrum Master and seasoned software developer, I've come to understand that sprint retrospectives are pivotal moments for fostering growth, enhancing team cohesion, and driving continuous improvement. In this guide, I'll walk you through my tried-and-true approach to conducting retrospectives that not only keep teams engaged but also catalyze meaningful change. By integrating these strategies, you can transform your retrospectives into powerful tools for team development and project success.

While this article focuses on facilitating effective retrospectives, the preparation phase is equally crucial. For a deep dive into planning retrospectives that address your team's specific needs, check out Crafting the Perfect Sprint Retrospective.

Solitude isn't about forced isolation or loneliness. It's not about escaping the world to live in seclusion. Instead, solitude is a deliberate practice of nurturing your state of mind to achieve inner freedom and clarity. In this post, we'll explore the transformative power of solitude and how it can enrich your life.

Your office might be making you sick — and you probably don't even know it. While you're focused on shipping features and hitting sprint goals, your workplace could be quietly undermining your health and performance.

Let's identify and tackle the most common workplace health hazards before they tank your productivity.

Your video meetings are probably leaking cognitive resources faster than a memory leak in production. What started as a temporary solution to stay connected during 2020 has become a permanent drain on mental bandwidth.

The problem isn't remote work itself — it's how we've implemented virtual collaboration. Let's optimize this system before it crashes your productivity entirely.

Your job search success depends on more than just your resume and interview skills. If your home office looks like a debugging session gone wrong, you're undermining your professional effectiveness before you even start.

Let's architect a workspace that supports your career goals instead of fighting against them.

Remote work doesn't require a dedicated office — it requires intentional space design. When you're competing with family activities, kitchen chaos, and living room distractions, you need to architect your workspace like you'd design a resilient system: adaptable, efficient, and optimized for your specific constraints.

Let's solve the space allocation problem without requiring additional infrastructure.