← Back to Skills Marketplace
nogara

Chief Feature Workflow

cross-platform ⚠ suspicious
437
Downloads
1
Stars
0
Active Installs
3
Versions
Install in OpenClaw
/install chief-feature
Description
Create and implement new features in Chief-managed projects using the Chief CLI. Use when asked to create a new PRD, implement a feature with Chief, set up a...
README (SKILL.md)

Chief Feature Workflow

Chief is an AI-driven development loop: reads a prd.json, implements user stories one by one via Claude Code, commits each, and tracks progress.

Full Workflow

1. Clone / verify repo

Confirm the project is cloned locally.

2. Create a new PRD

Run interactively in the project root:

cd \x3Cproject>
chief new \x3Cprd-name>

Chief launches Claude Code in PRD-writer mode. It will ask clarifying questions with lettered options. Provide:

  • The full feature description / spec
  • Answers to clarifying questions (e.g. "1A, 2C, 3D")

When Chief asks "Do you want to create prd.md?" — approve (option 1 or 2).

Chief converts prd.mdprd.json on /exit. Watch for:

✓ PRD converted successfully

Files land at: .chief/prds/\x3Cprd-name>/prd.md and prd.json

3. Create a worktree + branch

git worktree add ../\x3Cproject>-\x3Cprd-name> -b feat/\x3Cprd-name>
mkdir -p ../\x3Cproject>-\x3Cprd-name>/.chief/prds/\x3Cprd-name>
cp .chief/prds/\x3Cprd-name>/prd.{md,json} ../\x3Cproject>-\x3Cprd-name>/.chief/prds/\x3Cprd-name>/

4. Commit the PRD

cd ../\x3Cproject>-\x3Cprd-name>
git add .chief/prds/\x3Cprd-name>/prd.md
git commit -m "docs: add \x3Cprd-name> PRD"

Only commit prd.mdprd.json is typically gitignored.

5. Delegate to a subagent (recommended for long runs)

Instead of running Chief manually and polling, spawn a subagent to handle the full implementation autonomously:

Spawn a subagent with this task:
- Working directory: ~/\x3Cproject>-\x3Cprd-name>
- Run `chief \x3Cprd-name>` with pty:true
- Press `s` to start the loop
- Approve bash prompts with `1` + Enter (or `2` to always allow)
- If stuck on a prompt, send hex `0d` (Enter)
- Poll until all stories show ✓ (100%)
- Commit progress.md, push, open PR
- Announce the PR URL when done

The subagent runs fully isolated and auto-announces on completion. You can spawn multiple subagents in parallel — one per PRD/worktree — for concurrent feature development.

Parallel runs: 2–3 concurrent subagents is the practical sweet spot. Each Chief run is API-heavy (runs Claude Code under the hood), so more than 3 parallel runs risks rate limits and high cost.

5b. Run Chief manually (alternative)

If you prefer to supervise directly:

chief \x3Cprd-name>

Press s in the TUI to start. Chief works through stories in priority order, runs verification (make test, pnpm typecheck, etc.), commits each passing story, and updates progress.md.

Monitor via process(action=poll) on the PTY session. Watch for **US-00X is complete**.

6. Commit progress + push

git add .chief/prds/\x3Cprd-name>/progress.md
git commit -m "docs: add \x3Cprd-name> progress"
git push -u origin feat/\x3Cprd-name>

7. Open a PR

gh pr create \
  --title "feat: \x3Cprd-name>" \
  --body "Implements the \x3Cprd-name> PRD. See .chief/prds/\x3Cprd-name>/prd.md for spec." \
  --base main

8. Clean up the worktree

After the PR is merged:

cd \x3Cproject>
git worktree remove ../\x3Cproject>-\x3Cprd-name>
git branch -d feat/\x3Cprd-name>

Use git worktree remove --force if the directory has uncommitted changes.

Tips

  • TUI bash prompts: use 1 (Yes) or 2 (Yes, always allow)
  • If stuck on a permission prompt, send hex: ["0d"] via process(send-keys)
  • If a story fails, Chief retries or logs the failure in progress.md
  • prd.json is typically gitignored — only commit prd.md and progress.md
  • Chief resumes automatically from the last completed story if restarted

Reference

See references/chief-commands.md for CLI commands, TUI keyboard shortcuts, and official links.

About Chief

Chief is an open-source AI-driven development loop built by minicodemonkey.

Usage Guidance
This skill is coherent for automating Chief-based feature work, but review these practical points before installing: (1) Chief runs Claude Code and will observe repository contents and test outputs — do not use it on repos with secrets or sensitive data unless you accept that exposure. (2) The workflow expects git/gh credentials already configured; opening PRs will use those credentials and publish branches to your remote. (3) Spawning autonomous subagents can run long-lived processes and consume API/model credits — start with a small test PR in a safe repo or fork to confirm behavior. (4) If you don't already trust chiefloop.com / the Chief project, review their code/docs and run the CLI locally first. If you want more assurance, ask the publisher for a canonical homepage/repository link and verify the Chief CLI release sources before giving the skill network or repo-level access.
Capability Analysis
Type: OpenClaw Skill Name: chief-feature Version: 1.0.2 The skill is designed to automate a development workflow using the 'chief' CLI tool, which inherently executes project-defined code (e.g., `make test`, `pnpm typecheck`). The `SKILL.md` instructs the AI agent to 'Approve bash prompts with `1` + Enter (or `2` to always allow)' and to delegate the entire process to a subagent for autonomous execution. This combination creates a significant remote code execution (RCE) vulnerability, as the agent is instructed to trust and execute potentially malicious build/test scripts from an untrusted project without explicit human oversight. While the skill itself does not contain malicious code, it provides the mechanism for an agent to execute arbitrary code from a compromised or malicious project, classifying it as suspicious due to this high-risk capability.
Capability Assessment
Purpose & Capability
The name/description describe creating and implementing features using the Chief CLI and all runtime instructions are about running chief, creating worktrees, committing PRD/progress files, and opening PRs. There are no unrelated environment variables, binaries, or install steps requested.
Instruction Scope
The SKILL.md instructs the agent to run the Chief CLI (chief new / chief <prd-name>), spawn subagents to run long-lived interactive sessions (PTY), press keys/approve prompts, run verification commands (make test, pnpm typecheck), commit/push and open PRs. This is within the stated purpose, but it implies the agent (and the Chief/Claude Code service) will read and send repository content and test outputs to the AI backend — a potential data-exposure consideration that is expected for this workflow.
Install Mechanism
No install spec or code files are included (instruction-only). Nothing is downloaded or written by the skill itself, so there is no installation risk introduced by the skill bundle.
Credentials
The skill declares no required env vars, credentials, or config paths. The workflow assumes local tools (git, gh, chief) and existing repository/remotes are available; those are proportionate to the described tasks. Note: creating/pushing PRs requires Git/GitHub credentials already present in the environment, but the skill does not request or attempt to access them explicitly.
Persistence & Privilege
always:false and default autonomous invocation are used; the skill does not request permanent presence or modify other skills. The recommendation to spawn subagents allows long-running autonomous work, which increases operational reach but is consistent with the described feature-implementation workflow.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install chief-feature
  3. After installation, invoke the skill by name or use /chief-feature
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.2
Chief-feature v1.0.1 introduces support for spawning subagents to run multiple feature implementation loops in parallel. - New recommended workflow to spawn subagents for autonomous Chief runs, supporting parallel PRD implementation. - Added guidance on running 2–3 subagents concurrently for optimal throughput and resource usage. - Clarified manual vs. autonomous workflows, with detailed subagent instructions. - Added tips for resuming progress and proper file committing. - Cleaned up and clarified step order, emphasizing best practices for worktree management.
v1.0.1
- Added a recommended workflow using subagents to automate Chief feature implementation, enabling parallel PRD development. - Clarified the distinction between subagent and manual execution, providing guidance for both. - Included advice on parallel subagent usage and practical limits to avoid API rate limits. - Added tips for handling bash prompts, gitignored files, and Chief's resume behavior. - Reorganized and streamlined cleanup steps and overall workflow instructions.
v1.0.0
Initial release. Full end-to-end workflow for creating and implementing new features in Chief-managed projects: PRD creation via `chief new`, worktree setup, implementation loop via `chief <prd-name>`, progress commit, PR creation, and worktree cleanup.
Metadata
Slug chief-feature
Version 1.0.2
License
All-time Installs 0
Active Installs 0
Total Versions 3
Frequently Asked Questions

What is Chief Feature Workflow?

Create and implement new features in Chief-managed projects using the Chief CLI. Use when asked to create a new PRD, implement a feature with Chief, set up a... It is an AI Agent Skill for Claude Code / OpenClaw, with 437 downloads so far.

How do I install Chief Feature Workflow?

Run "/install chief-feature" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Chief Feature Workflow free?

Yes, Chief Feature Workflow is completely free (open-source). You can download, install and use it at no cost.

Which platforms does Chief Feature Workflow support?

Chief Feature Workflow is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Chief Feature Workflow?

It is built and maintained by Luiz Gustavo Nogara (@nogara); the current version is v1.0.2.

💬 Comments