How do I install the Development Flow skill?

Run npx skillmds@latest add tomevault-io/development-flow in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Development Flow safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Development Flow?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Development Flow free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Development Flow?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Development Flow by tomevault-io — Agent Skill

Name: Development Flow
Author: tomevault-io

Development Flow

This skill should be used when the user says "let's start working", "start development", "what should I work on", "check tasks", "fetch todos from github", "show my tasks", or at the beginning of any development session. Provides GitHub Project task sync and workflow management. Use when this capability is needed.

tomevault-io a28f6cf 2 files · 4.3 KB Updated Sep 17, 2026

File contents

Development Flow Guide

GitHub Project task sync with phase-based workflow tracking.

Project Configuration

Always read config first:

cat .claude/project.json

Variables:

PROJECT_NUMBER = .github.project.number
PROJECT_OWNER = .github.project.owner
REPOSITORY = .github.repository

Task Initialization

When starting a development session:

Read config: cat .claude/project.json
Check session todos (TaskList internal state)

If empty, fetch from GitHub:

gh project item-list {PROJECT_NUMBER} --owner {PROJECT_OWNER} --format json

Select task and create session todo

See references/task-init-flow.md for detailed workflow.

Task Execution Workflow

Status Flow

Todo -> In Progress -> To Review -> Done

Phase-Based Tracking

Use TaskCreate/TaskUpdate to track phases:

- Phase 1: Setup & Context (in_progress)
- Phase 2: Implementation (pending)
- Phase 3: Quality Check (pending)
- Phase 4: Sync & Complete (pending)

Mark each phase in_progress when starting, completed when done.

Execution Steps

Phase 1: Setup & Context

Read issue details: gh issue view <number> --repo {REPOSITORY}
Understand acceptance criteria
Identify affected files

Phase 2: Implementation

Follow task plan/AC
Apply KISS/YAGNI principles

Add task ID comments for traceability:

// See Issue #123
function newFeature() { ... }

Phase 3: Quality Check

Run lint: npm run lint
Run type check: npx tsc --noEmit
Verify tests pass

Phase 4: Sync & Complete

Update GitHub issue status
Close issue when done
Update session todo

GitHub Sync Commands

Fetch Tasks

gh project item-list {PROJECT_NUMBER} --owner {PROJECT_OWNER}
gh project item-list {PROJECT_NUMBER} --owner {PROJECT_OWNER} --format json

Create Task

gh issue create --title "Task title" --body "Description" --repo {REPOSITORY}
gh project item-add {PROJECT_NUMBER} --owner {PROJECT_OWNER} --url <issue_url>

Complete Task

gh issue close <issue_number> --repo {REPOSITORY} --comment "Completed"

Status Mapping

Session Todo	GitHub Issue	Project Status
`pending`	Open	Todo
`in_progress`	Open	In Progress
`completed`	Closed	Done

Critical Rules

Single task focus: Work on one task at a time
Phase tracking: Always use TaskCreate/TaskUpdate for phases
Quality gates: Run lint/typecheck before completing
Traceability: Add issue ID comments to new code
Sync back: Always update GitHub when task is done

Quick Reference

# Read config
cat .claude/project.json

# Fetch tasks
gh project item-list {PROJECT_NUMBER} --owner {PROJECT_OWNER}

# View issue
gh issue view <number> --repo {REPOSITORY}

# Close issue
gh issue close <number> --repo {REPOSITORY}

# Quality checks
npm run lint && npx tsc --noEmit

Flow References

Task initialization: references/task-init-flow.md
GitHub sync: references/github-sync.md
TDD process: references/tdd-process.md
Bug fix flow: references/bug-fix-flow.md

Source: juhyeonni/gas-sheets-query — distributed by TomeVault.

---name: development-flowdescription: This skill should be used when the user says "let's start working", "start development", "what should I work on", "check tasks", "fetch todos from github", "show my tasks", or at the beginning of any development session. Provides GitHub Project task sync and workflow management. Use when this capability is needed.---# Development Flow GuideGitHub Project task sync with phase-based workflow tracking.## Project Configuration**Always read config first:**```bashcat .claude/project.json```Variables:- `PROJECT_NUMBER` = `.github.project.number`- `PROJECT_OWNER` = `.github.project.owner`- `REPOSITORY` = `.github.repository`## Task InitializationWhen starting a development session:1. **Read config:** `cat .claude/project.json`2. **Check session todos** (TaskList internal state)3. **If empty, fetch from GitHub:** ```bash gh project item-list {PROJECT_NUMBER} --owner {PROJECT_OWNER} --format json ```4. **Select task and create session todo**See `references/task-init-flow.md` for detailed workflow.## Task Execution Workflow### Status Flow```Todo -> In Progress -> To Review -> Done```### Phase-Based TrackingUse TaskCreate/TaskUpdate to track phases:```- Phase 1: Setup & Context (in_progress)- Phase 2: Implementation (pending)- Phase 3: Quality Check (pending)- Phase 4: Sync & Complete (pending)```Mark each phase `in_progress` when starting, `completed` when done.### Execution Steps**Phase 1: Setup & Context**- Read issue details: `gh issue view <number> --repo {REPOSITORY}`- Understand acceptance criteria- Identify affected files**Phase 2: Implementation**- Follow task plan/AC- Apply KISS/YAGNI principles- Add task ID comments for traceability: ```typescript // See Issue #123 function newFeature() { ... } ```**Phase 3: Quality Check**- Run lint: `npm run lint`- Run type check: `npx tsc --noEmit`- Verify tests pass**Phase 4: Sync & Complete**- Update GitHub issue status- Close issue when done- Update session todo## GitHub Sync Commands### Fetch Tasks```bashgh project item-list {PROJECT_NUMBER} --owner {PROJECT_OWNER}gh project item-list {PROJECT_NUMBER} --owner {PROJECT_OWNER} --format json```### Create Task```bashgh issue create --title "Task title" --body "Description" --repo {REPOSITORY}gh project item-add {PROJECT_NUMBER} --owner {PROJECT_OWNER} --url <issue_url>```### Complete Task```bashgh issue close <issue_number> --repo {REPOSITORY} --comment "Completed"```## Status Mapping| Session Todo | GitHub Issue | Project Status ||--------------|--------------|----------------|| `pending` | Open | Todo || `in_progress` | Open | In Progress || `completed` | Closed | Done |## Critical Rules- **Single task focus:** Work on one task at a time- **Phase tracking:** Always use TaskCreate/TaskUpdate for phases- **Quality gates:** Run lint/typecheck before completing- **Traceability:** Add issue ID comments to new code- **Sync back:** Always update GitHub when task is done## Quick Reference```bash# Read configcat .claude/project.json# Fetch tasksgh project item-list {PROJECT_NUMBER} --owner {PROJECT_OWNER}# View issuegh issue view <number> --repo {REPOSITORY}# Close issuegh issue close <number> --repo {REPOSITORY}# Quality checksnpm run lint && npx tsc --noEmit```## Flow References- Task initialization: `references/task-init-flow.md`- GitHub sync: `references/github-sync.md`- TDD process: `references/tdd-process.md`- Bug fix flow: `references/bug-fix-flow.md`---> Source: [juhyeonni/gas-sheets-query](https://github.com/juhyeonni/gas-sheets-query) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions