CJ_goal_feature

Orchestrate feature development from design approval to a reviewable pull request.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/jcl2018/claude-skills-templates --skill cj-goal-feature
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: CJ_goal_feature
Source: https://github.com/jcl2018/claude-skills-templates/tree/main/skills/CJ_goal_feature
Command: npx skills add https://github.com/jcl2018/claude-skills-templates --skill cj-goal-feature

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the feature development process, taking a topic and orchestrating the creation of a reviewable pull request (PR) for human review.

Core Features & Use Cases

  • Feature Topic to PR: Converts a plain feature topic into a reviewable PR.
  • Design Approval: Includes an interactive design phase that requires approval before proceeding.
  • Silent Build: Performs the build automatically after design approval, stopping at the PR.
  • Resume Capability: Ability to resume from the last completed phase with validation before skipping.
  • Use Case: A developer has an idea for a new feature and uses this Skill to start the development process, which includes design approval, silent build, and finally the creation of a PR for review.

Quick Start

To start the process, run: /CJ_goal_feature "Add a new feature to increase user engagement"

Frequently Asked Questions about CJ_goal_feature

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

FAQPage Schema
How do I automate feature development from a topic to a reviewable pull request?

Automating feature development to a reviewable pull request involves orchestrating design approval, silent builds, and PR creation. This Skill converts a plain feature topic into a PR, requiring a clean git checkout and interactive design approval before proceeding with the automated build stages.

What is the process for getting design approval before an automated build?

Design approval before an automated build requires an interactive phase where the design summary is explicitly approved. Once approved, a silent subagent dispatches the build automatically, pausing the process at the pull request stage for human review rather than merging directly.

Can I resume feature development from the last completed phase after a failure?

Resuming feature development from the last completed phase is supported with validation checks before skipping. This ensures the automated build and orchestration process can recover safely from interruptions without restarting the design approval or prior build stages.

Do I need a clean git checkout to orchestrate feature development and PR creation?

A clean git checkout is required to orchestrate feature development and PR creation. The Skill executes commands in a controlled environment and relies on specific scripts, meaning a dirty repository state will prevent the automated build stages and silent subagent dispatch from running correctly.

Does automated feature orchestration work without office-hours design approval?

Automated feature orchestration does not work without office-hours design approval. The workflow explicitly requires human validation of the design summary before the silent build and pull request creation can proceed, ensuring proper oversight of the feature development process.