Use when a draft FeatureForge implementation plan needs a first-class fidelity review against the CEO-approved spec before engineering review
_REPO_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || pwd)
_BRANCH_RAW=$(git rev-parse --abbrev-ref HEAD 2>/dev/null || echo current)
[ -n "$_BRANCH_RAW" ] && [ "$_BRANCH_RAW" != "HEAD" ] || _BRANCH_RAW="current"
_BRANCH="$_BRANCH_RAW"
_FEATUREFORGE_INSTALL_ROOT="$HOME/.featureforge/install"
_FEATUREFORGE_BIN="$_FEATUREFORGE_INSTALL_ROOT/bin/featureforge"
if [ ! -x "$_FEATUREFORGE_BIN" ] && [ -f "$_FEATUREFORGE_INSTALL_ROOT/bin/featureforge.exe" ]; then
_FEATUREFORGE_BIN="$_FEATUREFORGE_INSTALL_ROOT/bin/featureforge.exe"
fi
[ -x "$_FEATUREFORGE_BIN" ] || [ -f "$_FEATUREFORGE_BIN" ] || _FEATUREFORGE_BIN=""
_FEATUREFORGE_ROOT=""
if [ -n "$_FEATUREFORGE_BIN" ]; then
_FEATUREFORGE_ROOT=$("$_FEATUREFORGE_BIN" repo runtime-root --path 2>/dev/null)
[ -n "$_FEATUREFORGE_ROOT" ] || _FEATUREFORGE_ROOT=""
fi
_FEATUREFORGE_STATE_DIR="${FEATUREFORGE_STATE_DIR:-$HOME/.featureforge}"
Before introducing a custom pattern, external service, concurrency primitive, auth/session flow, cache, queue, browser workaround, or unfamiliar fix pattern, do a short capability/landscape check first.
Use three lenses:
External search results are inputs, not answers. Never search secrets, customer data, unsanitized stack traces, private URLs, internal hostnames, internal codenames, raw SQL or log payloads, or private file paths or infrastructure identifiers. If search is unavailable, disallowed, or unsafe, say so and proceed with repo-local evidence and in-distribution knowledge. If safe sanitization is not possible, skip external search.
See $_FEATUREFORGE_ROOT/references/search-before-building.md.
For every interactive user question, use this structure:
RECOMMENDATION: Choose [X] because [one-line reason]A) ... B) ... C) ...Per-skill instructions may add additional formatting rules on top of this baseline.
docs/featureforge/plans/YYYY-MM-DD-<feature-name>.md.**Source Spec:** and load that exact spec path.featureforge:writing-plans.CEO Approved with **Last Reviewed By:** plan-ceo-review, stop and route to featureforge:plan-ceo-review.featureforge:writing-plans and featureforge:plan-eng-review.skills/plan-fidelity-review/reviewer-prompt.md when briefing the reviewer..featureforge/reviews/YYYY-MM-DD-<feature-name>-plan-fidelity.md.Review StageReview VerdictReviewed PlanReviewed Plan RevisionReviewed Plan FingerprintReviewed SpecReviewed Spec RevisionReviewed Spec FingerprintReviewer SourceReviewer IDDistinct From StagesVerified SurfacesVerified Requirement IDsReview Verdict must be pass for this gate to advance.After the reviewer writes the artifact, record the runtime-owned receipt:
"$_FEATUREFORGE_BIN" workflow plan-fidelity record --plan docs/featureforge/plans/YYYY-MM-DD-<feature-name>.md \
--review-artifact .featureforge/reviews/YYYY-MM-DD-<feature-name>-plan-fidelity.md
featureforge:writing-plans.featureforge:plan-eng-review.The terminal state is invoking featureforge:plan-eng-review only after a matching pass runtime-owned plan-fidelity receipt exists.