skills.rest
hadi-nayebi
hadi-nayebiCOMMUNITY
Explore all skills by this author →
𝕏@HadiNayebiGitHub

programmer

Execute Android backlog items with Gradle tests and health checks.

1|Updated Feb 17, 2026
Search Tags:#testing#implementation#backlog#scripts#android#continuous-integration#claude-md
One-click install
npx skills add https://github.com/hadi-nayebi/hadosh_android_app --skill programmer-hadi-nayebi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: programmer
Source: https://github.com/hadi-nayebi/hadosh_android_app/tree/main/.skills/programmer
Command: npx skills add https://github.com/hadi-nayebi/hadosh_android_app --skill programmer-hadi-nayebi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, jq, bc, and includes scripts (resource) components.

What problem does it solve?

The programmer Markov brain automates and governs implementation work on an Android project by reading PM context, selecting backlog items, producing focused plans, making minimal code changes, running tests and health checks, and recording results for future sessions. It reduces context-switching, prevents scope creep, and enforces project conventions so engineers can deliver reliable changes with clear handoffs.

Core Features & Use Cases

  • Backlog-driven implementation: Picks highest-priority OPEN items from docs/backlog.md and marks progress.
  • Context-first edits: Reads docs/programmer-brief.md and per-package CLAUDE.md before changing code.
  • Iterative loop: Plan -> Write code -> Write tests -> Run tests -> Run health check -> Record changes -> Update backlog.
  • Automated decision tools: Uses scripts to classify state, recommend next phase, detect scope creep, and log transitions.
  • Use Case: Triage a SEV-1 bug, implement the minimal fix, run unit tests and project health check, update CLAUDE.md, and mark the backlog item DONE with evidence.

Quick Start

Implement the highest-priority OPEN backlog item by reading the PM brief and package CLAUDE.md, plan a minimal change, write the code and tests, run tests and the health check, then update CLAUDE.md and docs/backlog.md.

Frequently Asked Questions about programmer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement Android backlog items using a CLAUDE.md context file?▼

To implement Android backlog items, the programmer reads docs/programmer-brief.md and per-package CLAUDE.md, plans minimal code changes, writes tests, runs Gradle checks, and updates docs/backlog.md. This enforces project conventions and prevents scope creep during package-level refactors and bug fixes.

What is the best way to automate Android bug fixes and prevent scope creep?▼

Automating Android bug fixes involves a structured iterative loop: plan, write code, write tests, run tests, run health checks, and record changes. The programmer Markov brain uses scripts to classify state, detect scope creep, and log transitions for reliable, focused implementations.

How do I run Gradle tests and health checks for Android package-level changes?▼

You run Gradle tests and health checks using provided scripts after making minimal code changes for an Android backlog item. The programmer executes these automated decision tools to verify implementation work, update CLAUDE.md, and mark the backlog item DONE with evidence.

Does the programmer Skill work with continuous integration scripts for Android apps?▼

Yes, the programmer Skill works with continuous integration by running Gradle tests and health checks via provided scripts. It classifies state, recommends next phases, and logs transitions to a local cache, ensuring Android implementations are verified before updating backlog files.

Do I need git and jq installed to use this Android implementation Skill?▼

Yes, you need git, jq, and bc installed. These dependencies support the programmer Skill's automated scripts that classify state, detect scope creep, log transitions, and coordinate Android implementation work with PM briefs and per-package CLAUDE.md files.

When should I not use an automated backlog-driven approach for Android app development?▼

You should avoid automated backlog-driven implementation for changes outside package-level scope or when lacking PM briefs and CLAUDE.md. The programmer Skill targets bug fixes, new features, refactors, and test writing coordinated with project conventions, not unstructured or cross-project modifications.

Related Skills

Explore More Software Engineering Skills→
duanegoodnerduanegoodner

kickoff_sprint_discussion

Categorize backlog items into themes and propose sprint priorities.

Community
Intermediate
MinhmiceMinhmice

code-reviewer

Inspect code diffs for security flaws, bugs, and maintainability issues.

Community
Intermediate
ManzuetiManzueti

health

Wrap project tools to compute a weighted codebase health score.

Community
Advanced
Kafil99Kafil99

constitution_guard

Validate project adherence to SDD principles and detect scope creep.

Community
Advanced